in reply to Re: The Cost of Nested Referencing
in thread The Cost of Nested Referencing

I agree for the most part, but sometimes you have to go for speed and sometimes, it's because it's not worth all the extra coding overhead. Most of these $self->{key}{subkey} items (in my code anyway) are because they satisfy my requirements, they are not sufficiently clustered to be considered their own object (I don't write OO for OO sake), or the number of times it will be accessed would make the extra level of indirection unacceptable performance-wise.


"To be civilized is to deny one's nature."
update: fixed typo.

Replies are listed 'Best First'.
Re: Re: Re: The Cost of Nested Referencing
by gjb (Vicar) on Nov 15, 2002 at 14:00 UTC

    Using Class::MethodMaker minimizes this effort of course.

    Of course, you're perfectly right that not everything maps to clases/objects.

    Regards, -gjb-