Re: Re: Re: Getting the next array element while still keeping the current one

That's one clear piece of code (w.r.t. doing everything in/around the main loop).

BTW, did you intentionally removed the warnings pragma or just forgot?

Comment on Re: Re: Re: Getting the next array element while still keeping the current one

Replies are listed 'Best First'.
Re: Getting the next array element while still keeping the current one by NetWallah (Canon) on May 03, 2004 at 16:32 UTC
I'm responding to the minor gripes that my code whines about "Use of uninitialized value in concatenation (.) or string..." under use warnings;. The only place where it complains is the print statement, which was intended to be a sample - the print was to be replaced by real code. The undef values in $p and $n are ligitimate for those boundary conditions. Offense, like beauty, is in the eye of the beholder, and a fantasy. By guaranteeing freedom of expression, the First Amendment also guarntees offense.	[reply]
Re: Re: Getting the next array element while still keeping the current one by parv (Parson) on May 05, 2004 at 04:58 UTC
Yes, no question about the fact of two values being undefined. I just wanted to clear the things, at least for myself; thanks.	[reply]