> -----Original Message----- > From: Randal L. Schwartz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 19, 2003 9:46 AM > To: [EMAIL PROTECTED] > Subject: Re: Control flow variables > > > >>>>> "Smylers" == Smylers <[EMAIL PROTECTED]> writes: > > Smylers> I also was under the strong impression that Larry had decreed > Smylers> that we wouldn't have chained statement modifiers ... but I > Smylers> thought it was because Larry had decided they would be a bad > Smylers> thing to have rather than because they aren't feasible. > > They weren't chained in Perl5, very deliberately. > > Larry added modifiers partially to get "do { } while $cond" to work, > and partially because he had used them in RSTS/E BASIC (which I've > also used, and recognized immediately). But when people started > nesting them, the code became incredibly unreadable quickly, so > no-nesting for Perl was a deliberate choice, not an implementation > detail.
This is surprising. Perl has never failed to provide me with an adequacy of rope in other places. Why get squeamish in this instance? > Unless Larry has come up with an overwhelming reason to permit them > after years of not having them, I doubt we'd see that (IMHO mistake) > in Perl6. Hmm. While I don't really expect to see leap year code written using nested modifiers, I think it would be nice to have each of them appear once: print for @a if $debug; =Austin
