You guys are beating a live horse. Apocalypse 5 already
discusses arrays pretending to be strings for the sake of parsing.
The capability has to be there, and in fact Patrick has been bearing
that in mind in the design of PGE. The only question for p6l is how
much syntactic sugar you want.
I've
Yuval Kogman wrote:
By the way, a nice use case for using the rules engine could be
"parsing" a stream of SAX events into a structure... XML::Simple in
perl6 could be really as simple as it sounds =)
Can anyone see this being retrofitted on top of current rules
semantics? How does PGE relate to t
On Wed, Jul 13, 2005 at 00:46:49 +0300, Yuval Kogman wrote:
> Perhaps the most interesting aspect of the string-is-a-list mindset
> is that Parsec can parse any list of crap into any structured crap.
> It's only affinity towards real strings and characters is the
> builtin library of useful rules.
On Tue, Jul 12, 2005 at 13:55:56 -0700, Larry Wall wrote:
> On the other hand, if the basic Str type is unwilling to take on the
> burden of being parameterized, we could generate all our funny string
> types by mapping a string name to an array declaration.
>
> my Str $foo is Array of byte;
On Tue, Jul 12, 2005 at 04:53:49AM -, David Formosa (aka ? the Platypus)
wrote:
: How do we intend to manipulate raw binary in Perl6? Perl5's use
: bytes; pragma is rather poor (forcing all strings to be raw in its
: scope or requiring do {use bytes; ...} type tricks to deal with them)
: and
How do we intend to manipulate raw binary in Perl6? Perl5's use
bytes; pragma is rather poor (forcing all strings to be raw in its
scope or requiring do {use bytes; ...} type tricks to deal with them)
and now Perl6 has real typing perhaps it would be more usefull to have
a bytestring type (or and
