??? 01/25/11 22:03 Modified: 01/25/11 22:03 Read: times |
#180793 - why fight? Responding to: ???'s previous message |
It's been some time and I am craving for some GOOD flamewar... ;-)
why 'fight'? the arguments both ways are relevant where applicable Neil Kurzman said:It is all about time. The Time to be a productive C Programmer is less then the Time it take to be equally skilled ASM Programmer. This is a very often quoted statement in favour of C in the C/asm flamewars, but I don't think this is true, at least not universally. And I don't think there is a relevant study supporting this. I do not know about 'universally' and I have a 'study': after decades of assembler only I was reluctantly dragged to 'C' and after another decade I am now at the point where I will use C as the first (but not only) choice. Also note, that none of us are to tell, based on personal experience, that a C programmer is more productive or what. ALL of us DO have the asm background the novices don't have anymore. see paragraph above and I do agree that to be reallygood at 'C' for the '51 you need to be good at asm (as noted I believe that in many cases an assembler module or two will be the right (maybe only) choice. Neil Kurzman said:I will assume the your code will be faster and smaller. maybe it fits into the next smaller chip.This is again an argument from the wars, in favour of asm, and is completely wrong as it completely misses the point, and is then turned around by the C fans. "fits into the next smaller chip " does not matter if you make a few, but if you make millions of units it does matter. I saved $0.89 by making a bit of code in asm instead of 'C' and for a production of 860.000 units, that is real money. The only relevant outcome of the programming process is a working program. And to achieve that, more than just "turning" is needed, and all those steps are the same or similar for all languages: problem analysis, program design, testing and debugging. you are missing two points: 1) maintainability by others than you and 2) with the lifetime of an embedded project, who can say that when you are long gone, the poor sod that has to "add a small feature" can even understand your asm. Erik |