Your message dated Fri, 22 Apr 2016 22:12:13 +0300
with message-id <[email protected]>
and subject line Re: Bug#319615: Why not for (EXPR; EXPR; EXPR) BLOCK continue
BLOCK ?
has caused the Debian Bug report #319615,
regarding Why not for (EXPR; EXPR; EXPR) BLOCK continue BLOCK ?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
319615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=319615
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: perl
Version: 5.8.7-3
Severity: wishlist
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
perlsyn says you can't have
for (EXPR; EXPR; EXPR) BLOCK continue BLOCK
(or at least doesn't list it as allowed). Unfortunately, perl seems to
agree:
$ perl -e 'for ($i = 0; $i < 10; ++$i) { } continue { }'
syntax error at -e line 1, near "} continue"
Execution of -e aborted due to compilation errors.
It'd be nice if that were possible...
- -- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (130, 'unstable'), (120,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.10-bohr
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages perl depends on:
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [
ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime
ii perl-base 5.8.7-3 The Pathologically Eclectic Rubbis
ii perl-modules 5.8.7-3 Core Perl modules
Versions of packages perl recommends:
ii perl-doc 5.8.7-3 Perl documentation
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC4lNQ+z+IwlXqWf4RAm1+AJ0TUxIfZVX5taOD3dOx7tNwbJwG6wCgiQEq
qGVnyWiGbhOJJTHwKkL6Ajs=
=Ul5L
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Thu, Sep 20, 2007 at 07:14:58PM +1000, Brendan O'Dea wrote:
> On Sat, Jul 23, 2005 at 10:25:20AM -0400, Anthony DeRobertis wrote:
> >perlsyn says you can't have
> > for (EXPR; EXPR; EXPR) BLOCK continue BLOCK
> >(or at least doesn't list it as allowed). Unfortunately, perl seems to
> >agree:
> >
> >$ perl -e 'for ($i = 0; $i < 10; ++$i) { } continue { }'
> >syntax error at -e line 1, near "} continue"
> >Execution of -e aborted due to compilation errors.
> >
> >It'd be nice if that were possible...
>
> Well internally perl implements
>
> for (EXPR1; EXPR2; EXPR3) BLOCK
>
> as
>
> EXPR1; while (EXPR2) BLOCK continue { EXPR3 }
>
> which makes adding a continue block a bit trickier. It does however
> suggest your solution, stash your contine expressions after ++$i:
>
> for ($i = 0; $i < 10; ++$i, CONT) { }
As the subject of this bug ('Why not...') has been answered and another
solution offered, I don't think there's any value in keeping this
wishlist bug open for another ten years. Feel free to take it upstream
if you care enough.
So closing. Sorry it didn't work out.
--
Niko Tyni [email protected]
--- End Message ---
