Thus, micro-libgcj is not even intended to be a strict subset of any
existing Java standard. If there is demand for such a subset, or a
complete J2ME implementation, micro-libgcj may be a good starting-point.
That's not a goal I'm interested in, though.
Cool I really like what your doing I've no doubt in my mind its the
right answer for a lot of embedded programming problems. Btw I looked
at replacing String with a utf8 C pointer. One thing preventing it was
the syncronization issue. The other was the methods on object. I
noticed you kept most of the methods of Object even though many are
empty. Making all the methods of Object final would allow you to
introduce subclasses of object like my utf8 string pointers that have
at most a one byte/bit object header that says there really pointers.
I did not work completly through if the header could be collapsed but
it would certianly open up the chance to replace objects with
efficient internal structures if we could ensure that they extend from
object and object itself has no overridable methods.
Have you considered removing or finalizing the methods of Object ?