 | | Re: interest in JVM porting effort
|
| (...) Actually, we can't do EmbeddedJava since that requires a full JVM including long and double, the Security manager, etc. We aren't going to be able to call it Java, since it won't pass the compatibility suite (we can say it implements a subset (...) (28 years ago, 7-May-99, to lugnet.robotics)
| | |  | | Re: Some comments (long)
|
| (...) For the record, up until recently I agreed with you. However, after hearing further discussions I think it is possible. The biggest hurdle is probably garbage collection since this is what causes Java's propensity to "gobble" memory. The class (...) (28 years ago, 7-May-99, to lugnet.robotics)
| | |  | | Re: interest in JVM porting effort
|
| Aaah, good points. Do we have a preliminary list of packages that we'll need? Actually, it's easier to pick things that aren't needed and then complement it. java.awt is right out, as is java.applet. The same thing can be said for java.beans, (...) (28 years ago, 7-May-99, to lugnet.robotics)
| | |  | | Re: interest in JVM porting effort
|
| (...) Actually, there are some things in java.math that should be there. I would expect we would have two sets of classes -- those which are built into the JVM port (ie, those required for operation like Object, Thread, etc) and those which can be (...) (28 years ago, 7-May-99, to lugnet.robotics)
| | |  | | Request for new list
|
| I request that the discussions of alternate firmware implementation details go into their own newsgroup now. Discussions about features can be crossposted to both lists. There were several requests recently to create a new group for newbies to (...) (28 years ago, 7-May-99, to lugnet.robotics)
| |