Godmar Back wrote: > Thinking about it, maybe it would even be worth thinking about > not implementing Strings as char[] arrays internally, but as utf8strings. > This would save space for all ASCII strings, it would allows to directly > use a literal's utf8 representation. Since strings are immutable, the > internal char[] array is never directly exposed anyway. It is done this way in gcj I think. But I do not suppose that it is a good thing for java only implementation - main aim for Strings should be efficiency. I think that String.charAt is method called often enough to cause major performance drop in entire java app with such strings. Artur
- 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