CompuServe Messages

Nope, your argument just went down in flames. It seems my Manx 32/16/8 statement was nothing more than wishful thinking… as you have no doubt seen, Keith reminded me that Manx shorts are 16 bits, not 8. So, Manx is just as strange (to my mind) as every other C compiler, and just as "standard" in that respect. I'll never understand why C is always 64/64/32 or 64/32/32 or 32/16/16 or 32/32/16 or… instead of a simple, logical, straightforward 32/16/8. Ah well, totally off the point (and it was an aside anyway, not really germaine to the discussion, in the first place). As long as I'm here, I trust you will allow me to comment on the other issues being bandied about. I tend to agree with you in regards to the use of ILAC. I can't see any reason offhand why it would HAVE to be there, it certainly could be a maintenance nightmare, and it would cause extra work in porting Manx->Lattice. However, I tend to agree with (I think it's) Larry in terms of the existance of the capability: it doesn't matter, or at least it shouldn't, and it certainly isn't something I could use to disrecommend a compiler. ("Don't buy Manx, it allows inline assembler!" Huh?) So how often do you use GOTOs in C, Ben? Rarely if ever, I would assume, because you seem to be a competent programmer. I think I've used a C GOTO once in my entire programming career, and that was for an embedded system <continued>