can work something out at some point
> later.
Any data pointer type, yes. It completely outlaws any attempt to
cast between data and function pointers though.
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
...Things are not as bad as they seem - they're worse
cific to different
language bindings - if you're embedding perl in C++ you probably
have an iostream, and if you're embedding in Java you'll have a
Java stream object. In each case you'll want an easy way to create
a PerlIO object from that.
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu
etter than lookahead here as you can always
jump back a bit after you change the lexer's state ;-)
> Parsing Perl is hard. Trust me. :)
Oh, you did say it again...
Parsing Fortran is fun as well. Whoever decided to allow spaces in
identifiers needs their head read...
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
...Who's on first?
a good trade off between simplicity for most
people and power for those that need it whilst still maintaining
type safety and maximum extensibility for things we havn't thought
of yet.
We might also still want a flags word to each of those routine for
things like your UTF8 flag.
Tom
--
Tom Hu
ms that provided the source from a string
or a file or whatever other wonderful data source somebody comes up
with.
The common case of parsing a string could of course be simplified
with a small wrapper function that created a string based stream
and then called the main parser entry point.
Tom
--
Tom
ay away from the print
statement.
Secondly in order to know that you needed to back up you'd have to
remember that you hadd had to guess that foo was a filehandle but
that it might also be a subroutine and it raises a whole serious of
questions about what other similar things you might need to re
inite lookahead you would never need to backtrack as you
could, if necessary, look right to the end of the program to decide
what the next token meant. Equally with no lookahead you will quite
likely need to backtrack unless your grammar is fairly restrictive, and
we all know that perl's grammar i
In message <[EMAIL PROTECTED]>
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 11:45 PM 11/21/00 +0000, Tom Hughes wrote:
>
> >Given that it isn't a valid C identifier, yes... Unless you're
> >using VAXC or DECC of course, which was your point I
ng...)
>
> Or Perl$parse_script, but that's a matter of taste, I suppose. :)
Given that it isn't a valid C identifier, yes... Unless you're
using VAXC or DECC of course, which was your point I assume ;-)
Tom
--
Tom Hughes ([EMAIL PROTECTED])
http://www.compton.nu/
...Discoveries are made by not following instructions.
