>
>I have a suggestion. You have an specific application. You really need an
>application specific language. C and Pascal are good when you have a variety
>of problem domains that you want to write software for. General purpose
>languages add a lot of necessary complexity in order to be general purpose.

In the AVR, and in the PIC, I've written bytecode interpreters.
These let you define only the commands you need, and the language can 
be as simple as you like.

In the PIC, it was for a software controlled transmitter, I 
implemented 16 commands, with "skip" on conditionals like "Skip -3 if 
input active"

The first implementation I ever worked on, was for the Verifone 
transaction terminals, which we called "TCL".
Over time, it grew quite complicated, but everything was task oriented.
The first TCL program written for a customer was "MNL"
   M ;read the Magstripe
   N ; priNt it
   L ; Loop back and do it again.

A lot of code in those commands, but to the TCL programmer, very simple.
Verifone has the manual on their web site, might give you some ideas.


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist