I'm inclined to say "yes", but really it's part of a larger set of PIR
language features we might want to look into:
1) The ability to say where the PIR code starts, so we can provide a
separate stub header ("perl -x")
2) The ability to say where the PIR code ends, so we can include other
information in the file thereafter ("__END__")
3) The ability to get access to the information in the file after the
__END__ ("<DATA>" and "__DATA__" In perl5)
Any of these features alone would be nice but not necessary. Together
I think they open up a lot of flexibility. I would, however, prefer to
use something more PIR-ish than "__END__", maybe ".endfile" instead.
--Andrew Whitworth
On Tue, Dec 1, 2009 at 11:30 PM, Jonathan Leto <[email protected]> wrote:
> Howdy,
>
> Do we want __END__ in PIR?
>
> https://trac.parrot.org/parrot/ticket/1118
>
> Duke
>
> --
> Jonathan "Duke" Leto
> [email protected]
> http://leto.net
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev
>
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
