Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!uwvax!oddjob!gargoyle!ihnp4!homxb!houxs!daw
From: daw@houxs.UUCP (D.WOLVERTON)
Newsgroups: comp.lang.c
Subject: Some questions about ANSI C
Message-ID: <497@houxs.UUCP>
Date: Thu, 6-Aug-87 13:58:16 EDT
Article-I.D.: houxs.497
Posted: Thu Aug  6 13:58:16 1987
Date-Received: Sat, 8-Aug-87 12:28:50 EDT
Organization: AT&T Bell Laboratories, Holmdel
Lines: 30
Keywords: underscore Paris standard C declarations


I have some questions regarding the ANSI C standardization process
that I haven't seen addressed in comp.lang.c:

1) I read recently (in the C Journal?) that the name space available
   to users might be increased to include some identifiers which begin
   with an underscore.  Has this been discussed by the Committee?

2) Is a report forthcoming regarding the results of the Paris meeting?
   [Perhaps from Doug?]

3) What is the current timetable for standardization?

4) dpANSI C, as I read it, requires that a conforming hosted implementation
   contain *no* declarations (including prototypes) or #defines for 
   user-space identifiers not defined by the Standard, in order to avoid name 
   space pollution.  This implies that declarations for library functions 
   supplied by an implementation but not defined by the Standard which 
   currently exist in one of the standard headers must be moved elsewhere.
   Where does the Committee or P1003 (POSIX) plan to put these gypsy 
   declarations?  Won't this break existing (UNIX application) code?

I would also like to take this opportunity to thank those on the net who
take the time to explain all those picky little details of C.

--------------------------
David Wolverton
..!houxs!daw

"A little song, a little dance, a little seltzer in your pants." - Monty Python