11:18 PM
To: Velocity Developers List
Subject: Re: JavaCC memory problems [was: Re: Problems with build
Velocity]
Did "ant test" pass?
It'd be interesting to see an example high-memory use case and get a
feel for what percentage this lowers the memory use.
WILL
On 3/13/07, Sylwe
; }
> > > >
> > > > currentTemplateName = "";
> > > > -
> > > > +token_source.clearStateVars();
> > > > +if (velcharstream!=null) velcharstream.Done();
> > > > return sn;
-
> > > +token_source.clearStateVars();
> > > +if (velcharstream!=null) velcharstream.Done();
> > > return sn;
> > > }
> > >
> > >
> > >
> > > 2007/3/12, Ryan Smith <[EMAIL PROTECTED]>:
&g
>
> > >
> > >
> > > 2007/3/12, Ryan Smith <[EMAIL PROTECTED]>:
> > > >
> > > >
> > > > Will,
> > > >
> > > > Where would you put the code to call the Done() method and free up the
> &
tream.Done();
> > return sn;
> > }
> >
> >
> >
> > 2007/3/12, Ryan Smith <[EMAIL PROTECTED]>:
> > >
> > >
> > > Will,
> > >
> > > Where would you put the code to call the Done() method and free up the
> &g
> > memory?
> >
> > We currently doing profiling of Velocity as well and are trying to find
> > places exactly like this.
> >
> > Ryan
> >
> > -Original Message-
> > From: Will Glass-Husain [mailto:[EMAIL PROTECTED]
> > Sent: Monday, Mar
Sylvester,
It looks like the "ant parser" task was not properly cleaning up after
itself. I've made a revision to the build files that should fix this.
Typing
ant clean
ant parser -Djavacc.home=\your\javacc\path
ant compile
should now work fine.
WILL
On 3/10/07, Sylwester Lachiewicz <[EMAIL
s well and are trying to find
> places exactly like this.
>
> Ryan
>
> -Original Message-
> From: Will Glass-Husain [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 12, 2007 2:47 PM
> To: Velocity Developers List
> Subject: Re: JavaCC memory problems [was: Re:
ing of Velocity as well and are trying to find
places exactly like this.
Ryan
-Original Message-
From: Will Glass-Husain [mailto:[EMAIL PROTECTED]
Sent: Monday, March 12, 2007 2:47 PM
To: Velocity Developers List
Subject: Re: JavaCC memory problems [was: Re: Problems with build
, 2007 2:47 PM
To: Velocity Developers List
Subject: Re: JavaCC memory problems [was: Re: Problems with build
Velocity]
Thanks for the tips! Definitely something to investigate.
WILL
On 3/12/07, Sylwester Lachiewicz <[EMAIL PROTECTED]> wrote:
> Hi,
>
> today JavaCC works fine - mayb
Thanks for the tips! Definitely something to investigate.
WILL
On 3/12/07, Sylwester Lachiewicz <[EMAIL PROTECTED]> wrote:
Hi,
today JavaCC works fine - maybe there was bad day ;)
I run profiler with simple velocity app (2 .vm file, simple merge) and found
that internal by design CharStream
Hi,
today JavaCC works fine - maybe there was bad day ;)
I run profiler with simple velocity app (2 .vm file, simple merge) and found
that internal by design CharStream has method :
---
/**
* The lexer calls this function to indicate that it is done with the
stream
* and hence implementatio
Hi Sylvester,
Thanks for the note on the build script. It really needs to check for
a min of 1.6.
I'm not sure why you have problems compiling. I use javacc 3.2 as
well. Did you type "ant clean" first?
JavaCC generates node files and Parser.java. The node files are not
needed and can be del
13 matches
Mail list logo
