chromatic <chromatic@wgz.org> writes: > my $input = Iterator::Files->new(@filelist); > while (<$input>) { ... } Yes, except that the constructor takes other arguments as well. I've currently implemented: my $input = Iterator::Files->new( files => \@filelist ); > Creating a new API in 2008 which requires the localization of a > magic global to do something obvious seems wrong to me. The question remains to what level it must be compatible with the current <> implementation. When a file list is passed, I'd say that @ARGV should remain untouched. But should ARGV, $ARGV and ARGVOUT still reflect the status of the iterator, as they do with <> ? -- Johan