To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / 4942
4941  |  4943
Subject: 
Re: Some comments (long)
Newsgroups: 
lugnet.robotics
Date: 
Fri, 7 May 1999 13:15:16 GMT
Viewed: 
1007 times
  
Kekoa Proudfoot wrote:


I'm not so sure on the backwards compatibility thing.  Can you rattle off a
list of reasons why that might be useful?  Here's my list of pros/cons:

+ less firmware reloading for some (since new firmware works as old did)
+ less changes to NQC compiler
+ OCX still works, and so do existing tools
- limits flexibility; cannot reorganize opcode space
- OCX cannot use new features, and is thus somewhat useless
- new tools need to be written no matter what


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
can be".

But, is that what legOS is?  Trying to remember back to the genesis of this thread
- is the only complaint about legOS that it's too difficult to
install/learn/program in?  Or are there limitations in legOS that would be overcome
in a complete re-architecture of the bytecode?  (I'm planning to jump into legOS
and find out for myself, soon - as soon as I "finish" my current bot.)

Thanks,
Mark David



Message has 1 Reply:
  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 (...) (25 years ago, 7-May-99, to lugnet.robotics)

Message is in Reply To:
  Re: Some comments (long)
 
(...) Assuming you use the ROM to receive things, which would be prudent in terms of space but not strictly necessary, the lengths of the opcodes in the message receiving code are determined by the lowest three bits of the opcode: 0 means length 0, (...) (25 years ago, 6-May-99, to lugnet.robotics)

42 Messages in This Thread:













Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact

This Message and its Replies on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR