Dare I start pointing out that the compiler doesn't generate the machine code? The assembler and linker generates the machine code. The compiler generates platform specific assembler code.
Dare I start pointing out that the compiler doesn't generate the machine code? The assembler and linker generates the machine code. The compiler generates platform specific assembler code.
Dare I start pointing out that the compiler doesn't generate the machine code? The assembler and linker generates the machine code. The compiler generates platform specific assembler code.
Now and again I write assembler and it gets turned into machine code. Sometimes I write C and it gets turned into "insert anything you like in these quotes" and eventually machine code. The rest is just semantics.
hi Mike,
Rem: that N-m query.
In an idle moment, I figured that if you held out at full arms length, two 750mL cans of fourX larger that would be 1.5N-m.
No many people know that.EDIT: Cr*p, I forgot about Nigel.! I guess he would know...
Did you see my correction from Ojisan >> Ojiisan.?
There are many different C compilers from different vendors, different countries, however, a good one does save time.
Sometime, it is so hard to find one.
Especially for the newest chips, e.g. the dsPICs. I tried both Microchip C30 and Hi-tech DSPICC, both of them are too buggy to be trusted for right now.
I heard Hi-Tech's C is no longer as good as it was before... can't confirm myself.
I use C30... and yeah sometimes it's a bit buggy depending what you want to do. Sometimes it's not a compiler issue.. but one of those 4575445 errata and/or silicone release