Re: Here there be cammels!

[Anonymous Monk]

I have tried setting $.

Interestingly:

while (<DATA>) { chomp; warn "<$_>"; }
warn "One";
$. = 123;
warn "Two";
close DATA;
warn "Three";
$. = 456;
warn "Four";
__DATA__
Zero

Gives:

<Zero> at - line 1, <DATA> line 1.
One at - line 2, <DATA> line 1.
Two at - line 4, <DATA> line 123.
Three at - line 6.
Four at - line 8, <DATA> line 456.

And yet, it's a hack. Better to implement the message yourself.

[LanX]

> And yet, it's a hack.

Looks like a bug for me, though DATA is closed it's reported at FOUR.

Only b/c a line-number is set.

> Better to implement the message yourself.

Well, yeah, undocumented behavior. :)

[Discipulus]

I do not think is a bug: is a edge case of use of very particular features...
diamond <> never close the handle and __DATA__ is very near to be $0 in this case (if i remember you can seek it and print the main program too). Because you can adjust $. and you had not closed DATA handle you end with the beahviour observed.
from perldata

Text after __DATA__ may be read via the filehandle PACKNAME::DATA , where PACKNAME is the package that was current when the __DATA__ token was encountered. The filehandle is left open pointing to the line after __DATA__. The program should close DATA when it is done reading from it.

PS. thanks for the line directive hint: never eard about..
L*

[Anonymous Monk]

Using DATA was just an example, the same thing happens on a normal filehandle too.

system 'echo "foo" >/tmp/blah';   
open my $fh, '<', '/tmp/blah' or die $!;
while (<$fh>) { chomp; warn "<$_>"; }
warn "One";
$. = 123;
warn "Two";
close $fh;
warn "Three";
$. = 456;
warn "Four";
__END__
<foo> at - line 3, <$fh> line 1.
One at - line 4, <$fh> line 1.
Two at - line 6, <$fh> line 123.
Three at - line 8.
Four at - line 10, <$fh> line 456.

So LanX is probably right about it being more of a bug than an obscure feature :-)