Hi, J2ME is split into two things, the VM specification and the profile. MIDP is the profile, not the VM. The VM follows either the CDC specification (Connected Device) or the CLDC specification (Connected Limited Device). Here again, we now have two versions, 1.0 and 1.1 (CLDC1.1 is specified in JSR 139).
Most phones were originally CLDC1.0/MIDP1.0. However, newer devices are all MIDP2.0. CLDC 1.0 was integer only, but 1.1 supports floating-point. It also supports weak references -- this is a subset of the J2SE weak reference classes, so the gap is getting smaller. Rob. On 11/1/05, David N. Welton <[EMAIL PROTECTED]> wrote: > Geir Magnusson Jr. wrote: > > Do you really mean J2ME for a specific purpose? > > Yes, 'j2me' is vague... Since MIDP is the lowest common denominator, I'd > start with that. > > > What we want to do here is a modular system to which you can easily > > replace parts as appropriate for your usage, either to port to a new > > platform or usage/performance profile.... > > MIDP has a lot of things missing - you need to make sure you don't have > any of that deeply mixed up in your core, or else ripping it out gets to > be difficult. No floats, no doubles, no reflection, just off the top of > my head. > > -- > David N. Welton > - http://www.dedasys.com/davidw/ > > Linux, Open Source Consulting > - http://www.dedasys.com/ >