> We do have to worry about the C<next> loop control function though.
> It's possible that in
>
> FOO: while (1) {
> next FOO if /foo/;
> ...
> }
>
> the C<FOO> label is actually being recognized as a pseudo-package
> name! The loop could well be an object whose full name is C<MY::FOO>.
> Or something like that. But maybe that's a gross hack. Seems a bit
> odd to overload C<next> like that. Maybe we need a different word.
I don't want to get accused of too much bikeshed-painting :-), but seems
like "more" would work:
$line = more $FOO;
This also connotes generalized incrementing, so it serves that purpose too.
And, hey, there's "less" for decrementing too!
-Nate
- Re: Apoc2 - <STDIN> concerns Stephen P. Potter
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns Michael G Schwern
- Re: Apoc2 - <STDIN> concerns James Mastros
- Re: Apoc2 - <STDIN> concerns Graham Barr
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns James Mastros
- Re: Apoc2 - <STDIN> concerns Michael G Schwern
- Re: Apoc2 - <STDIN> concerns David L. Nicol
- Re: Apoc2 - <STDIN> concerns Larry Wall
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns Graham Barr
- Re: Apoc2 - <STDIN> concerns Dan Sugalski
- Re[2]: Apoc2 - <STDIN> concerns A. C. Yardley
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns Larry Wall
- Re: Apoc2 - <STDIN> concerns David L. Nicol
- Re: Apoc2 - <STDIN> concerns John Siracusa
- Re: Apoc2 - <STDIN> concerns Richard Proctor
- Re: Apoc2 - <STDIN> concerns Nathan Wiger
- Re: Apoc2 - <STDIN> concerns David L. Nicol
