Re: [Oopic-compiler-devel] Re: Asking the community... WAS: Re: [Oopic-compiler-devel] Testing...

[Neil D. <nd...@us...>]

Andrew Porrett wrote:
> At 03:29 AM 4/30/2004 +0100, Neil Durant wrote:
> >Agreed.  Let's put some work into a really well thought out feature list
> >and present it only when we're pretty sure we can implement these things
> >(ie after seeing the op-code definitions and some subsequent pondering).
> >Then we can "go public" with our plans and it won't look like
> >vapourware/dreamware.
> 
> Yes, we need to take a long, hard look at the .oex files that are uploaded
> to the OOPic.  This will tell us what sort of useful stuff we can do.  For
> example, I'm pretty sure that the start of the file has an object list
> definition that is used to build the actual objects in RAM.  Once the real
> objects are in RAM, the list in the EEPROM is ignored.  How easy would it
> be to have a new object list copied there and then trigger a reset of the
> processor - instant change of available objects.  Just don't try to access
> an object that doesn't exist any more.  Obviously, you'd need to branch to
> the appropriate object initialization routine right after the reset, etc.
> 
> I need a solid breakdown of everything that can be done in a .oex file to
> come up with more goodies.

Indeed - there could be all sorts of nifty features we could exploit!

Neil
-- 
Neil Durant
<nd...@us...>