[antlr-interest] Changes to C runtime for 3.4

[Jim Idle]

Thanks, I will look in to that. Perhaps a last minute change broke it.
However, the string stuff is only supported for 8 bit and UCS2 characters
in the runtime as I don't want to write all that code for every encoding,
when it is just a convenience thing that has caused more trouble than it
is worth. I must have taken out the init of that method in UTF8 mode.

Jim

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of Julien BLACHE
> Sent: Friday, June 24, 2011 10:10 AM
> To: antlr-interest at antlr.org
> Subject: Re: [antlr-interest] Changes to C runtime for 3.4
>
> Jim Idle <jimi at temporal-wave.com> wrote:
>
> Hi Jim,
>
> > 1)      The distinction between ASCII and UCS2 input streams is now
> removed
> > and there is a single function: antlr3FileStreamNew() to replace the
> > file related input streams and a function" antlr3StringStreamNew to
> > replace the memory related input streams. Prototypes and usage:
>
> antlr3StringStreamNew() crashes by calling a NULL funcptr when creating
> a new UTF8 stream.
>
> At the bottom of the function, input->strFactory->newStr8() is NULL.
>
> JB.
>
> --
> Julien BLACHE
> <http://www.jblache.org>
> <jb at jblache.org>                                  GPG KeyID 0xF5D65169
>
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-
> email-address