CompuServe Messages

I have responded to your message and indicated that the function you diagrammed is ill-conceived. Even so, it is no indication that the assembly code is required to be next to the c code, unless the only criteria is that the function be written in c – which I won't buy. As per the compiler discussion, I recommend Lattice – you go ahead and recommend Manx, if that's your preference, or both, or neither, or individual evaluation, or Modula. or whatever. Gyrations depend on the application… you know that. I don't think that the compiler issue is one that needs any more debate from me; because I don't feel that strongly about it. I prefer Lattice – I can help people if they use Lattice; I can share code with them; and vice-versa; I won't see any inline asm. And if I were to see emit stuff, rest assured they wouldn't get the flames out till the next ice age! But the odds of seeing emit are miniscule… it's major league hard to generate, while #asm stuff is trivial to generate in comparison. by the way – Lattice currently defaults to the same setup that Manx uses, re 16 bits and etc; I don't use the standard configuration since they made that change, which was at 4.0 or thereabouts. So you don't need gyrations at this point… not that it matters. –Ben-