erik malund wrote:
-------------------------------
The "opcode injection" method (eg Bryan's asm{} keyword) seems easy if you consider that each 'C' source line produces a distinct piece of object; but - especially with modern optimising compilers - this is not necessarily the case! Thus, although the position of the "injected" opcode may seem obvious in the source file, the corresponding position in the generated object could be a bit more tricky!

Is this not the Gatesian Idea, "we will make it more difficult for you to do what you want to do, so you will do what we want you to do" ?

The compiler, to the best of my knowledge, generates assembly source regardless.

Besides Bryan claim to have the best optimiser, so it can't be a big hurdle.

Erik


Actually the compiler doesn't generate assembly source with the asm{} insertion method. Remember it requires the opcode to work and just inserts the opcode where specified.

Bryan