On Sat, 4 Dec 2004 01:37:00 -0800, Larry Wall <larry@wall.org> wrote: > for =$*IN {...} > for =$*ARGS {...} Yay. A generalised form of the input operator, which can create even handier idioms for simple file processing. Maybe I wasn't clear enough. My issue wasn't specifically with '.lines' for filter behaviour -- as a replacement solely for the while (<>) { ... } idiom, it would be quite adequate. But as a replacement for <OPENEDFILE>, it is (IMO) sub-par, and definitely does add to the length of the whole. As for the "nuclear blackmail" argument: One of the prime reasons I like Perl is that different things look different. When everything starts looking like a method call, that distinction rapidly drops away. > $file = =<foo.c>; Huh. That's really kinda neat. > But here's the kicker. The null filename can again represent the > standard filter input, so we end up with Perl 5's > > while (<>) {...} > > turning into > > for =<> {...} Which is really short for 'for =@*ARGS {...}', then? -- Schwäche zeigen heißt verlieren; härte heißt regieren. - "Glas und Tränen", MegaherzThread Previous | Thread Next