Path: utzoo!mnetor!uunet!husc6!hao!oddjob!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.lang.c Subject: Re: unofficial X3J11 meeting notes Message-ID: <9753@mimsy.UUCP> Date: 13 Dec 87 21:57:14 GMT References: <6829@brl-smoke.ARPA> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 24 Keywords: ANSI C standard In article <6829@brl-smoke.ARPA> gwyn@brl-smoke.ARPA (Doug Gwyn ) writes: >A new keyword, "noalias", was added; it's a type-qualifier like const >and volatile. Its only function is to permit tighter optimization.... Aside from the obvious---that noalias can be applied to globals and aggregates, and that some dumb compilers still use the word `register' to decide what to put into registers---what is the difference between this and `register'? That is, why not simply allow register to be applied to globals and aggregates? >Pointers to the same object are now guaranteed to compare equal. >All types of null pointer compare equal. (char *) and (void *) >have the same representation. Is this temporary? That is, is this something that is noted to be liable to change in a future standard? >NULL and size_t are to be included in any header that references them >in the Standard.... Since size_t is presuably a typedef, not a #define, this sounds ugly. -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690) Domain: chris@mimsy.umd.edu Path: uunet!mimsy!chris