Al,
And now for reality: of course if we set out to imitate the implementation allowing $, we'd better imitate it. The question is what to watch out for and how to avoid buggering the tokenizer in process.
If sparse is going to imitate a VAX implementation then how $ is glued is probably the least of the implemention worries. VAX C supported a whole host of extensions (eg, the ability to glue comments, 8 & 9 in octal constants). I have a pdf of the DEC C language reference manual for Tru64 which people are welcome to a copy of.
I don't have access to VMS boxen (thanks $DEITY);
Continuing in the vein of Irrelevant, AFAICS. You can access various Crays here: http://www.cray-cyber.org/access/index.php Perhaps there is a similar site available for Vaxes?
IOW, we need documentation of the native compilers to find out which kind of behaviour is expected.
I collect old C compiler manuals, if anybody locates a ps or pdf of an original VAC C compiler manual, please forward me a copy. -- Derek M. Jones tel: +44 (0) 1252 520 667 Knowledge Software Ltd mailto:[EMAIL PROTECTED] Applications Standards Conformance Testing http://www.knosof.co.uk - To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
