View Single Post
  #11   Spotlight this post!  
Unread 05-10-2003, 16:30
Dave Flowerday Dave Flowerday is offline
Software Engineer
VRC #0111 (Wildstang)
Team Role: Engineer
 
Join Date: Feb 2002
Rookie Year: 1995
Location: North Barrington, IL
Posts: 1,366
Dave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond reputeDave Flowerday has a reputation beyond repute
Quote:
Originally posted by rbayer
c) I haven't seen a formal spec for the language yet. (Please don't say implement all of C. That's about the same as writing a C compiler, which is a HUGE project and one that I doubt anyone here has the time to take on).
Rob,
Why try to interpret the C code as it runs? As you say, implementing all of the language constructs would be a lot of work. It would be much more efficient to just compile the user's RC code into a native library on the host's workstation and then link it in at runtime... I would think that would simplify the porting of your application quite a bit. Most likely IFI will provide some sort of library for the RC that will have some standard functions for reading inputs, writing outputs, setting PWMs, etc., so all you'd have to do is provide the same interface for the user's code to work with.

Besides, it'll be much harder to interpret programs written for the new processor and maintain real-time speed than it was with the pokey BASIC Stamp.