EasyC Wish List

[dcbrown]

Ok, don't get me wrong - we like EasyC, but...

I'm finding that we're using "User Code" more and more within all the routines being written. So I thought I'd start a wish list for EasyC.

1. Defines with arguments and these showing up in the user functions list.
For example:

#define SetLeftWheel( _pwm ) SetPWM(2, _pwm)

Yeah, we could code a routine called SetLeftWheel() that simply calls SetPWM(), but the call stack isn't that large and we could end up wasting a lot of its stack entries on simple redirection. The define just makes it easier for us to forget which ports/pins/interrupts go together to make up a specific feature on our robot. A feature for Pro mode only maybe?

2. Storage classes/qualifiers for variables.

static rom near int lookup[42]={0,8,8,8}; for example.

Another Pro only feature?

3. Global "User Code".

Currently we need to define a lookup table that is created readonly in program memory. We're using user code to do this and then initializing the array within a routine. The routine then must be called to access an array member. We'd like to be able to put some user code into a global area so the array can be used by more than one routine easily.

4. Cut & Paste support

In input boxes and being able to copy out the source lines from the source view window. Or an export function that exports the source lines into a straight text C file.

5. PrintToScreen()

We're using hyperterminal so we can save our debug output to a file easier. It needs \r\n at the end of prints to get to the start of a new line. Unfortunately we can enter "Data is %d mgs\r\n" - we'd like to add the %d format character ourselves and then select the variable. Maybe a check to see if a format selection is already present and then just add the variable to the end of the line? Because we can't output multiple variables per PrintToScreen() call, we've been using the following:

PrintToScreen( "Data1, Data1, Data3\r\n");
user code[ PrintToScreen( "%d, ", data1 ); ]
user code[ PrintToScreen( "%d, ", data2 ); ]
user code[ PrintToScreen( "%d\r\n", data3);]

Maybe if there was a selection box to enable/disable adding the newline at the end. We print out the data this way so it can be pulled into an excel spreadsheet and charted easily.

6. The ability to use the Ctrl key to add to and accumulate sets of code to
cut/delete etc. Select an line item, hold down the Ctrl key and select
another line item, etc.

7. A defined upgrade path from EasyC to MPLab.
As programmers become more adept and comfortable with programming. They should be able to easily grow from EasyC to MPLab and carry their work with them. This would promote quick prototyping in EasyC but support programmers growth to using MPLab. At the moment the transition is abrupt and you have to start again in MPLab. Maybe an Export Project to MPLab function to create the sources/includes and a template MPLab project or instructions for using the new sources and WPI lib from MPLab. (Ok, I admit it - I tried hacking apart the BDS file to do this but didn't get anywhere other than being able to do some fundamental record breakdown/breakout).

I'm sure there might be others. But these are the ones we have at the moment.


DCBrown