| ??? 02/15/07 19:30 Read: times |
#133082 - That's the kind of nonsense... Responding to: ???'s previous message |
... that gets coding standards a bad name.
Any coding standard that fails to recognise that there will be specific areas where the rules have to be "broken" is completely worthless! Such blatant uselessness utterly discredits the standard, which will tend to lead to it also being incresingly ignored in other areas where it could add value! Any decent coding standard must allow for the cases where the rules have to be broken, so that these can be highlighted and treated with special care and attention - particularly in terms of documentation & review. David Lewis said:
Unfortunately, the company's coding standards are against the use of assembler quoting reasons of longer to debug, harder to maintain and harder for new coders to be able to take over projects. Are you misrepresenting them here? Sure, assembler tends to be "harder" - that just means that you have to pay particular attention to ensure that your assembler is not like that. Hence the standards should allow assembler where its use can be specifically justified. There should be no problem in your case - especially if it is confined to just the ISR! |
