Re^3: Should we bother to save hash lookups for performance? (yes, sometimes)

for($self->{center}{floor}{room}{bay}{rack}{unit}{port}) {
    last if --$_->{timecount};

    close($_->{handle}), last
        unless $_->{transmitted} or $_->{received}

    $_->{timecount} = $_->{timeout};
    $_->{transmitted} = $_->{recieved} = 0;
}
[download]

Makeshifts last the longest.

Comment on Re^3: Should we bother to save hash lookups for performance? (yes, sometimes) Download Code

Replies are listed 'Best First'.
Re: Re^3: Should we bother to save hash lookups for performance? (yes, sometimes) by BrowserUk (Patriarch) on Oct 19, 2002 at 20:59 UTC
...BUT, BUT, BUT...it was only pseudo-code.... Aristotle++ You can tell its a slow weekend at PM when you start optomisiing my pseudo-code:) Cor! Like yer ring! ... HALO dammit! ... 'Ave it yer way! Hal-lo, Mister la-de-da. ... Like yer ring!	[reply] [d/l]
Re^5: Should we bother to save hash lookups for performance? (yes, sometimes) by Aristotle (Chancellor) on Oct 19, 2002 at 21:05 UTC
Oh, I wasn't just being facetious. :) I meant that you can use `for` in Perl like you use `with` in Pascal. Larry himself called `for` a "topicalizer". I love it for that use, too. I'll even use it as an expression modifier to topicalize a variable for a single expression like I said in my previous reply on this thread. Makeshifts last the longest.	[reply]