??? 11/29/05 16:47 Read: times |
#104373 - Not only but also Responding to: ???'s previous message |
Erik Malund said:
My experience is that most such happen when a PC programmer is tasked with coding embedded and try to force the PC methodology down on the poor little '51. I have seen projects that did not work because of things like "I use the huge model because I can not be bothered with memory selection" and "using printf in an ISR is not a problem" and "using malloc saves memory". I think it is even worse than that. I have seen many a so called 'embedded' software engineers that can only write in C and have zero concept of what the techniques, structures and algorithms translate into in terms of assembly code size, speed and resources usage. We were once (forced) to subcontract the development of a Chinese character input method to a Chinese software company because they understood the method and the Chinese characters. The result was unbelieveably slow. They swore blind it could not be made faster and the fault was with our parts of the software (you know the story) and of course our client belived them. Eventually we got hold of the source and found they had passed a huge structure by value instead of by reference. Simply fixing that resulted in a 5 fold speed increase. Ian |