in reply to Re: Design Question
in thread Design Question

This was actually pretty quick to implement, so I've tested it out and it works great. I do need the array outside of common_stuff so I didn't use a closure. This approach seems to get exactly what I want without the necessity to clean-up a global. Are there any negatives with doing things this way that I should be aware of? The main problem I saw is that it required a change to the argument-lists for some functions.

Replies are listed 'Best First'.
Re: Re: Re: Design Question
by TomDLux (Vicar) on Aug 07, 2003 at 03:44 UTC

    Beginner/Intermediate programmers are sometimes intimidated by an array reference or hash reference. The way I see it, they think ( or someone tells them ) that referenceces are complicated, so they get frightened and do things wrong.

    Since you know that references are actually quite easy, you should be fine. It takes a slight bit of effort to keep track of when a variable is actually a reference to a hash, so you can use it properly, especially when deealign with something several layers dow a data structure.

    But testing as you write code (Test:;Simple and test::More), and use of the Perl debugger and Data::Dumper when something doesn't seem right, will get you lots of working code in no time.

    --
    TTTATCGGTCGTTATATAGATGTTTGCA

[reply]

      Beginner/Intermediate programmers are sometimes intimidated by an array reference or hash reference. The way I see it, they think ( or someone tells them ) that referenceces are complicated, so they get frightened and do things wrong.

      I agree with you. Maybe if perl newbies could see references as sort of pointers, they could found them easier to understand.

      ----------
      kral
      (sorry for my english)
[reply]

In Section Seekers of Perl Wisdom