Re: Programming Program
 

It sounds like you're unfamiliar with just how powerful and capable EasyC can be. I know I was until recently.

If you're serious about writing code, then a text-based IDE like MPLab wins. However, programming can be much more productive when it focuses on creating and implementing algorithms instead of on producing syntactically correct lines of text. It's a different level of programming, one which demands a different kind of focus from the programmer, but I think it's worth putting forth the initial extra effort in order to gain the benefits of faster and more reliable results.

I think the purpose of those views is so that you can verify that you're getting out what you expect. Of course you can't edit the C text -- a large part of the tool's purpose is to make syntax and semantic errors a non-issue, so letting you mess with the uncompiled intermediate representation of the program would be bad.

Re: Programming Program
 

[rant]

Point taken.

I somewhat disagree with that statement. It's only faster to write a program in EasyC if the program is relatively simple. E.G. Default tank drive, click & drag. However, once you get into more complicated programs, with loads of variables, and arrays, EasyC becomes a nightmare (especially with arrays). It's incredibly hard to keep organized in EasyC. You can't even see local variables in a function unless you either open up a new window, or have the "C" window open. Also you can't re-organize the list of user functions, the functions are put in order and you can't move them around.

Question: If "syntax and semantic errors [are] a non-issue", then why do you need to verify that the output code is correct? And if someone doesn't know the syntax of C, then how are they supposed to know what to "expect"?

[/rant]