Hi,
well, it is a good theme to be discussed in infinity loop (=
In fact, there is nothing bad with usage of any language - even basic... Most my projects for 51s have been written at ASM. Even current projects which occupe more than 60kb of binary program code, are still in ASM. Okay, I use C and C++ as well. For example, the complex device is PC plus a custom board with T89C51CC03. As result, c51 program is in ASM; program for PC is in Visual C++ (with some ASM custom routines). Why? It is the main question. Let do the red line here.
1) Writing ASM routines, I do know that it is only me who responses for all bugs/features/side effects of the work. If I used the Ñ or another high level language then I would have trusted in people who had created all these compilers/linkers/optimizers etc. I have nothing against those people :) but there are tasks in which I cannot allow "third-party" bugs just because I love people and would not like the airplane crash due they errors (as example :) Here it is the simplest formula: my errors * third-party errors.
2) For me, C language is very useful if you do program in high-equipment environment with alot of libraries, devices, drivers etc. It is nice to write Delay(50); instead type some lines in ASM (you know, what I talk about :)
3) Sometimes when I am looking on C programs for C51 I cannot understand why does author use the C. For example, I see EA=1; and cannot understand why not SETB EA. So my opinion is: using of C-language is not bad way but ask yourself:
- is it realy needed (there are many libraries, hard framework or what?) or just a modern KeWl show m/;
- are you ready to get third-party bugs?
The last thing I know exactly: at ASM you will pay no more time than with C in simple/custom projects. Many people talk me that C-language does economy the time - no, it is wrong often and often. Especialy when I remember about crashes of these airplanes...
cu