Jenda Krynicky wrote:
> From: Steve Bertrand <st...@ibctech.ca>
>> I'm going to have to really focus on learning about the dereferencing
>> factor, and where/when some of the [${}->] etc need to be, because I
>> don't have a very good grasp on that.
>
> Try the perlreftut man page.
> (http://perldoc.perl.org/perlreftut.html)Thanks again Jenda, I've been trying to clean up a system left for me eight years ago. It spans hundreds of files, with 10s of thousands of lines of code. Over the years, I've written modules to try to absorb some of the code-reuse and modularize it so that the system can interact with a DB along side the hundreds of thousands of individual text files in use. The last few days I've really made progress and learnt quite a bit. I'm amazed at how well some of the modules I wrote actually work, and how efficient they are. I also very much like dealing with the 'black box' while not having to change the APIs for the legacy apps that I originally tried to make work by tapping them into my modules. FWIW, I just started deploying Config::Tiny and I find it incredible, and have picked up on many other techniques unknown to me previously. I really need to focus on #perldoc perlreftut, and aside from that, I need to learn how to properly format my perldoc section of my modules (I do write very descriptive information about my API's, but they only read nicely when viewing the .pm. They show up without newlines in perldoc). Here's to a few steps forward! (Thanks to "Perl Objects, References & Modules" where I got my first understanding of OOB in Perl. Looks like I'll have to do another re-read). Steve
smime.p7s
Description: S/MIME Cryptographic Signature
