Re: [Jython-users] jython on WinCE/iPaq update

[<bc...@wo...>]

[Brian Zhou]

>It works!
>
>But a few observations and questions:
>
>1. I saw entries like
>
>    JYTHON-PACKAGE-com.ibm.oti.vm
>
>    in the pre-indexed jython.jar, does that mean this jython.jar is
>bootstrap classes specific? 

Yes to some extend.

>Can I use the same jython.jar for Sun Personal Java for WinCE/ARM?

Yes, but you can't import any of the sun specific non-public classes.
Since you shouldn't do that anyway, it is no great loss.

>2. I'm thinking about document all this, but will this pre-index feature be
>in the next release?

I don't know yet. It depends on how usefull it is. Feedback like this
makes it easier to decide.

>3. The previous pystone boost was not by VAME 1.4 upgrade. Using pre-indexed
>jython.jar pystone falls back to 48-49. It was more because I happened to
>extract the classes.zip into a directory. This also indicates pre-index in
>the jar has some overhead.

It should be minimal but the feature does add an addition lookup for a
resource with the name JYTHON-PACKAGE-* when an import statement doesn't
find any another match.

>4. "import re" throws StackOverflownError while "import _sre" works.
>Attached is the stack trace.

At first look it doesn't seem like a bug but a real stack overflow. Can
you extend the amount of stack space allocated? It looks like the javaCC
parser isn't optimized for small stacks (but neither if jython).

regards,
finn