Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site harpo.UUCP
Path: utzoo!decvax!harpo!uucp
From: uucp@harpo.UUCP (uucp)
Newsgroups: mod.ber
Subject: net.lang.c
Message-ID: <2568@harpo.UUCP>
Date: Mon, 2-Jul-84 11:16:09 EDT
Article-I.D.: harpo.2568
Posted: Mon Jul  2 11:16:09 1984
Date-Received: Mon, 2-Jul-84 17:35:23 EDT
Organization: AT&T Bell Laboratories, Whippany
Lines: 75
Approved: ber@gummo.UUCP

Summary of net.lang.c for period 6/15/84 - 7/1/84
    as seen at utah-gr by Spencer Thomas 
    Articles 2015 - 2069 (55 articles)

                Continuing discussions

unsigned - yes, you can say "unsigned short" and "unsigned long".
	Not according to K&R!  Well, maybe.  Depends on which part of K&R
		you read.
	Interesting sidelight: the "V7" C compiler just translates short
		into int, so you can't say "short int", but you can say
		"long short"!

Side effects inside sizeof - changes to pcc to detect and warn about them.
	Apparently the draft standard says that side effects inside sizeof
		will not occur.

C vs Algol style semicolon usage (terminator vs separator)

(How quickly they forget!)  Further discussion (under a new title) of
	appending tokens using cpp.
	Note: ANSI standard will not allow token formation by the
	pre-processor.

HQTF2: NULL as a pointer value (wasn't it only last month we ran this one
	into the ground?  It's getting as bad as "FOO" was on unix-wizards.
	Maybe it's time for an addition to the "Netiquette" guide! :-)

                New discussions

Is "a;" a legal declaration as "a" as an int?
	Arguments from the C Reference Manual say it isn't (good!), but
		some compilers accept it.

How do people do variable length structures?  (Usually with a string
	on the end.)
	Subdiscussion about 0 vs 1 length arrays for this purpose.

6809 C compiler and 8 bit ints - what do you do on machines where 16 bit
	arithmetic is horrendous?

Short discussion of argument substitution into macro definitions.

ANSI X3J11 committee has issued a draft standard for the C language, also
	including library and environment standards.

Question about default case in switch statement.
	Reasonable answer explaining why it's not a problem.  (See the 
		discussion for more info.)
	A cute program showing some really gross things about case statements.


Revised strings package posted to net.sources (by ok@edai.UUCP).

Chem Abstracts is looking for work done in the area of portability standards
	or guidelines.  Contact cbosgd!chemabs!bobr (Bob Richards).

C compiler for 8051 (but must go to object code, NOT 8051 assembler.  According
	to the author, this makes it a "true compiler".)  Contact Scott Abbot,
	ihnp4!mvuxa!sa.

Crossover from net.micro.pc: if "double a[10][20]", is "a" the same as
	"&a[0][0]"?  No - they are the same address, but different types.

Looking for pipes in Aztec C (sdcsvax!sdccs6!ix244@berkeley - John Antypas).

How to change the C compiler so it doesn't do arithmetic in double precision?
	(Ki@MIT-OZ)

Question about forming a standard way to distinguish System V, System III,
	Version 7, BSDx, ... programs from each other.  Can we agree on
	a set of #defined symbols for each?  Mail to ihuxx!ignatz (Dave Ihnat).

Looking for Ctrace debugging tool (ala SP&E April 1984) (Rich Altmaier -
	decwrl!ios!richa)