If you want to write a fast parser for XML, preventing backtracking is
going to be quite essential. I suspect the problem is your grammar,
not the grammar engine itself. You could post it to perl6-users and
ask for advice on it.
Leon
On Thu, Jun 4, 2009 at 7:25 AM, Richard Hainsworth wrote:
> Is
Hi,
Following my last reasoning on implicit threading and implicit
event-based programming[1], I came to two interesting realizations...
1 - Every object is potentially lazy, not only lists.
2 - Lazy doesn't mean "wait until I need the data", but "don't stall me
because of that data".
That bas
HaloO,
Daniel Ruoso wrote:
So the questions are:
* Are there any imperative barriers in Perl 6?
I would think that at least every method call is a barrier.
An object's lifetime is a sequence of states and methods are either
returning information about the state or calculate a new state. The
On Thu, Jun 4, 2009 at 9:57 AM, TSa wrote:
> HaloO,
>
> Daniel Ruoso wrote:
>>
>> So the questions are:
>>
>> * Are there any imperative barriers in Perl 6?
>
> I would think that at least every method call is a barrier.
> An object's lifetime is a sequence of states and methods are either
> retu
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20090610T00Z
DTEND:20090610T03Z
DTSTAMP:20090605T035153Z
ORGANIZER;CN=jason switzer:mailto:jswit...@gmail.com
UID:g3rsts66avsaacp817n7ri1...@google.com
ATTEND
