On May 9, 11:24 am, Attila Szegedi <[EMAIL PROTECTED]> wrote:
> Well, if it were proper JSON, you could use either a Java or JS based
> JSON parser... Next best thing is turning off compilation and trying
> to use Rhino interpreted mode.
>
> Attila.
>
> On 2008.05.09., at 17:16, scroyston wrote:
>
> > I've got a large javascript object I'd like to load and access from
> > rhino. It's essentially a database table, i.e.:
> > rows: {[
> > [row 1 data],
> > [row 2 data],
> > [row 3 data]...
> > ]};
>
> > It's not 'conformant' JSON because it has things like 'new Date(...)',
> > etc.
>
> > When I try to compile it with Rhino, I get a bytecode error of being
> > over a 64K limit (I believe this is a limitation of the JVM, not
> > rhino).
>
> > I was hoping someone might have a suggestion about accessing this kind
> > of data through rhino. Efficiency is extremely important.
>
> > Thanks
And eval() always uses interpretive mode, so you could probably
compile most of the script and eval the pseudo-JSON.
--Norris
_______________________________________________
dev-tech-js-engine-rhino mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
