>
>
> On Thu, 3 Feb 100, Godmar Back wrote:
>
> Ok, that sounds like a plan. The only other problem I noticed is that
> Kaffe seems to use plain char* types for class names. These class names
> really should be in unicode strings or at least UTF8 strings. The
> current Kaffe implementation means that a \0 embedded in the class name
> will screw up code that expects a \0 at the end of a string. One
> of the regression test checks for this.
>
We should probably keep all descriptors/identifiers that were derived
from uft8consts in the constant pool as utf8consts all the time.
- Godmar
- Re: large Class.forName() patch Archie Cobbs
- Re: large Class.forName() patch Jason Baker
- Re: large Class.forName() patch Patrick Tullmann
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Jason Baker
- Re: large Class.forName() patch Mo DeJong
- Re: large Class.forName() patch Mo DeJong
- Re: large Class.forName() patch Archie Cobbs
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Mo DeJong
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Alexandre Oliva
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Artur Biesiadowski
- Re: large Class.forName() patch Godmar Back
- Re: large Class.forName() patch Artur Biesiadowski
- Re: large Class.forName() patch Dan McGuirk
- Re: large Class.forName() patch Godmar Back
