mod.std.c Digest V3 #8
Orlando Sotomayor-Diaz
osd7 at homxa.UUCP
Sun Feb 24 01:37:01 AEST 1985
mod.std.c Digest Sat, 23 Feb 85 Volume 3 : Issue 8
Today's Topics:
\e, string concatenation
ARPANET Readers Only
----------------------------------------------------------------------
Date: Sat, 23 Feb 85 3:31:25 EST
From: Doug Gwyn (VLD/VMB) <cbosgd!ucbvax!gwyn at Brl-Vld.ARPA>
Subject: \e, string concatenation
To: cbosgd!std-c at BERKELEY
I am opposed to \e unless the spec insists on ISO/ASCII character
set, since not every character set has a suitable character for \e.
I am not all that happy with the new \a "alarm" character either.
Adjacent string concatenation is very useful in getting what one
wants out of preprocessor macros. (See example I sent to INFO-C.)
[ If you are an ARPA reader, please read below. ]
------------------------------
Date: Sat, 23 Feb 85 10:00:00 EST
From: The Moderator <cbosgd!std.c>
Subject: ARPANET Readers Only
Once more is time to explain how mod.std.c is forwarded from USENET to
ARPA.
USENET
------ ARPANET
-------
------<----------<----cbosgd!std-c at Berkeley.ARPA
| ^
| ^
mod.std.c ------->-----| |
(ANSI C) | ----------
|------->| INFO-C |-->| INFO-C |->|
| |
net.lang.c ------->----| |
(K&R C, etc.) | |
^---------<------|--------<--------------<---------|
We arranged the above to save the time of creating a new ARPA list
for ANSI C. So, if you are a reader in ARPA, please submit your
ANSI C related contributions to cbosgd!std-c at Berkeley.ARPA, it
will get to INFO-C. Plese do so in consideration to USENET, at least.
Orlando Sotomayor-Diaz, Moderator, mod.std.c.
------------------------------
End of mod.std.c Digest - Sat, 23 Feb 85 10:29:31 EST
******************************
USENET -> posting only through cbosgd!std-c.
ARPA -> ... through cbosgd!std-c at BERKELEY.ARPA (NOT to INFO-C)
In all cases, you may also reply to the author(s) above.
More information about the Mod.std.c
mailing list