|Perl Monk, Perl Meditation|
Trouble is that at over 1000 pages it's sometimes hard to know what to read. Starting at the start and reading through would not only be time consuming but brainfully painful. Still, I will try and go and read up on this topic now, this post having identified something I should perhaps know more about.
Added Later:Just read a section called "Names" in Programming Perl (the first section* listed in the index under /lexical scopes/). It was quite interesting and I probably got 50% of what it was saying. I suspect to get any more though I'd have to re read it, read all the sections it refers to, read it again, re the sections it refers to again etc etc. Still maybe in time that'll all happen and I'll understand 51% of lexical scopes ;-)
*I work on the naive assumption the first section will be the most meaningful as well as the easiest to understand.
Added Even Later:(After posts by dragonchild and pfaut).
First comment - I didn't make the original post but I think people realise that.
dragonchild - I see where you are coming from, I admire your commitment and would wish to work along similar lines. I'd like to say though, that for me scripting in perl (I can't call what I do programming but I guess that's a whole other debate) is something I do for fun and occasionally because it's useful :-). It's not core to my job although I am trying to progress in that direction. That said I can't say I'm very dedicated to reading NT books either. Doing what you want to is great, if you can afford to. In reality I don't mind what I'm doing and it pays better (2-3x) that I'd get as a trade apprentice, if I could even get an apprenticeship.
pfaut - Thanks for the pointers on how to use 'PP'. Sounds a bit silly but using a book is more difficult that just reading it and you've given me appreciated direction and enlightenment. I got it for reference but now see that I could also use if for learning too. I've been messing about with Perl for about 18 months so I've written a couple of scripts, the latest (on my scratchpad), was actually written mainly as an exercise in using hashes and recursion with subroutines.