[antlr-interest] More, Status of C++ backend?
Ruslan Zasukhin
sunshine at public.kherson.ua
Wed Jan 2 22:18:01 PST 2008
On 3/1/08 2:08 AM, "Jonathan T" <jonathan.thomas at ca.com> wrote:
Hi Jonathan,
> V2 duplicated the input stream all over the place, resulting in the high
> number of string allocations/deallocations that you are seeing. You want to
> optimise the actual allocation/deallocation. What about removing them
> altogether?
Even better.
Yes I need read latest docs yet, and check v3 deeply.
> Gavin probably put it better further down in this thread
> QUOTE ... I wasn't proposing going and using std::string as a member of the
> token or anything. You'd do it the same way as the Java runtime works --
> normally store only indexes, but create a string on demand. ... END_QUOTE
Okay, although I will suggest use not indexes as Java, but direct char*
pointers.
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
More information about the antlr-interest
mailing list