 | | Re: Some comments (long)
|
|
(...) Thanks, I think I understand how it works. John A. Tamplin Traveller Information Services jat@LiveOnTheNet.COM 2104 West Ferry Way 256/705-7007 - FAX 256/705-7100 Huntsville, AL 35801 -- Did you check the web site first?: (URL) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
Kekoa Proudfoot wrote in message ... (...) Do you think it would be possible with improved firmware to support inline H8 code embedded in a user program? For example, a special byte code could indicate that the following code should be executed (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some more comments and suggestions.
|
|
Well, now that you mention it... lugnet.robotics.rcx.misc might be the best way to go. That seems to have the most consistency with existing groups. If that group's discussion splinters considerably, then new groups could be created in the l.r.r.* (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
(...) Good idea! I like it! The only problem I can see with this is I'm not sure if the H8 supports position independant code or not. If it does, then there's no problem. (...) (28 years ago, 6-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
(...) You might be able to do this if you were clever about it; you might be able to define an opcode that defines a native subroutine that you can call with another opcode, say, that passes in 16- or 32-bit values in registers and expects you store (...) (28 years ago, 7-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long) (was: Something else is needed, I think...)
|
|
(...) I should clarify this. The 16-bit software multiply takes two 16-bit numbers and stores their product in a 16-bit number. The 32-bit software multiply takes two 32-bit numbers and stores their product in a 32-bit number. The operations are (...) (28 years ago, 7-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) At the risk of splintering the development efforts here from 2 to three, I've been wondering the same thing. I guess I'm not as concerned with ensuring that my existing OCX code works - I'd rather see any new OS make the RCX "be all that it (...) (28 years ago, 7-May-99, to lugnet.robotics)
|
| |
 | | Re: interest in JVM porting effort
|
|
In message <Pine.A32.3.91.99050...iveonthene t.com>, John A. Tamplin <jat@liveonthenet.com> writes (...) Good for you! If you have an achievable goal then get cracking. I would offer help but my HelloWorld applet skills are not really the ticket. (...) (28 years ago, 7-May-99, to lugnet.robotics)
|
| |
 | | Re: interest in JVM porting effort
|
|
This sounds reasonable. I imagine we'll be using the EmbeddedJava API for this, as this allows us to implement only the parts of Java we need or can support in the RCX. I'm a bit disappointed with the minimal info that java.sun.com provides on what (...) (28 years ago, 7-May-99, to lugnet.robotics)
|
| |
 | | Re: Some comments (long)
|
|
(...) There are no limitations in LegOS at all that I am aware of. The biggest problems with LegOS are the size of and number of tools required work with it and the learning curve for people who don't have any prior programming experience (let alone (...) (28 years ago, 7-May-99, to lugnet.robotics)
|