Nice. But you need to discuss the initial condition: I'd guess you need
an
implicit
=begin perl
before line 1 of each script file, so that scripts that don't pod still
work.
How about some extensions, which integrate another old perl5 feature?
Instead of __END__, how about
=begin data
Now that works for a single DATA file handle, but we (probably) also
need to
=end all
=begin data
which takes two lines, rather than __END__'s one line.
So then we speculate about combinations: if "begin", "end", and "handle"
were
prevented from being pod processor names, we could
=begin perl
=end perl begin pod
=begin perl
=end all handle data
=end data handle data2
=handle data3
seen by data2 and data3 handles!
=end all begin perl
This would restrict data from containing lines beginning with =, or at
least lines
beginning with =end, =begin, =handle, or =for. Could "escape" with \=
or == or ???
--
Glenn
=====
There are two kinds of people, those
who finish what they start, and so
on... -- Robert Byrne
____________NetZero Free Internet Access and Email_________
Download Now http://www.netzero.net/download/index.html
Request a CDROM 1-800-333-3633
___________________________________________________________
