> Am 13.11.2013 um 18:19 schrieb "Sean P. DeNigris" :
>
> Norbert Hartl wrote
>> Producing the output immediately often has the drawback that it is hard to
>> alter the stream in between...
>
> I've had success outputting-as-I-go in the ==> block, instead of, or in
> addition to returning the t
Norbert Hartl wrote
> Producing the output immediately often has the drawback that it is hard to
> alter the stream in between...
I've had success outputting-as-I-go in the ==> block, instead of, or in
addition to returning the token...
-
Cheers,
Sean
--
View this message in context:
http:
Am 13.11.2013 um 13:15 schrieb Federico.Balaguer :
> Thanks Norbert for your kind reply.
>
> My only reminding question is about the input. PetitStream are made from the
> contents of another stream. So, if I have a readStream on a file and I
> convert it to PetitStream, it will end up loading
Thanks Norbert for your kind reply.
My only reminding question is about the input. PetitStream are made from the
contents of another stream. So, if I have a readStream on a file and I
convert it to PetitStream, it will end up loading the entire content of the
file on memory.
Could it be possib
Am 12.11.2013 um 23:02 schrieb Sean P. DeNigris :
> Federico.Balaguer wrote
>> Hello,
>>
>> I am developing a parser with PetitParser and one of the options I would
>> like to try is to get my parser to read from an external stream (file) and
>> produce the output to another external stream (ano
Federico.Balaguer wrote
> Hello,
>
> I am developing a parser with PetitParser and one of the options I would
> like to try is to get my parser to read from an external stream (file) and
> produce the output to another external stream (another file)
>
> Is this possible? I found that Stream>>asPe
