On Sat, 16 Jun 2001, Casey Lucas wrote:
> > Jasper already understands what things like do, and it
> > generates specialized code to implement the required functionality (rather
> > than treating it like a custom tag).
>
> right. i thought he might be refering to custom tags. that's where my
"Craig R. McClanahan" wrote:
>
> On Sat, 16 Jun 2001, Casey Lucas wrote:
>
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > On Fri, 15 Jun 2001, Casey Lucas wrote:
> > >
> > > >
> > > > Costin,
> > > >
> > > > sounds good.
> > > >
> > > > btw, when do you think the generator code in 34 will settle
On Sat, 16 Jun 2001, Casey Lucas wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > On Fri, 15 Jun 2001, Casey Lucas wrote:
> >
> > >
> > > Costin,
> > >
> > > sounds good.
> > >
> > > btw, when do you think the generator code in 34 will settle down
> > > a little?
> >
> > Soon :-)
> >
> > There
On Sat, 16 Jun 2001, Casey Lucas wrote:
> ok. just let me know when you think it's appropriate to
> start adding some tag optimizations.
I assume the changes will be local to 2-3 generators and runtime. We
should be able to have them in parallel, it would generate some conflicts
in cvs but we c
[EMAIL PROTECTED] wrote:
>
> On Fri, 15 Jun 2001, Casey Lucas wrote:
>
> >
> > Costin,
> >
> > sounds good.
> >
> > btw, when do you think the generator code in 34 will settle down
> > a little?
>
> Soon :-)
>
> There is only one more change in the generator layout - switching to
> a "visitor
On Fri, 15 Jun 2001, Casey Lucas wrote:
>
> Costin,
>
> sounds good.
>
> btw, when do you think the generator code in 34 will settle down
> a little?
Soon :-)
There is only one more change in the generator layout - switching to
a "visitor" pattern, with the tree representation of the page se
Costin,
sounds good.
btw, when do you think the generator code in 34 will settle down
a little?
-casey
[EMAIL PROTECTED] wrote:
>
> Ok, time to discuss the first mini-optimization.
>
> Right now jasper has 2 ways to output data - one is the common
> out.println("String ");
>
> The other (
+1
[EMAIL PROTECTED] wrote:
>
> Ok, time to discuss the first mini-optimization.
>
> Right now jasper has 2 ways to output data - one is the common
> out.println("String ");
>
> The other ( not very used ) is using an additional file to store the
> strings, and it's enabled by "largefile" opti
Ok, time to discuss the first mini-optimization.
Right now jasper has 2 ways to output data - one is the common
out.println("String ");
The other ( not very used ) is using an additional file to store the
strings, and it's enabled by "largefile" option.
The output system is probably the most
