Path: utzoo!attcan!uunet!mcvax!ukc!cam-cl!am From: am@cl.cam.ac.uk (Alan Mycroft) Newsgroups: comp.lang.c Subject: Random type questions and oddity. Message-ID: <326@scaup.cl.cam.ac.uk> Date: 19 Sep 88 17:01:50 GMT References: <530@accelerator.eng.ohio-state.edu> <1988Aug28.030747.19105@utzoo.uucp> Sender: news@cl.cam.ac.uk Reply-To: am@cl.cam.ac.uk (Alan Mycroft) Organization: U of Cambridge Comp Lab, UK Lines: 14 In article <1988Aug28.030747.19105@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: >> foo; >Actually, in an X3J11-conforming compiler, you get an error message. >You can't default both type and storage class in X3J11 C. True for the case listed, but not for functions definitions. For some reason known only to the committee, ANSI C proposes to allow *f() { return 0; } any many similar of this ilk. I suppose the justification was to preserve nonsense like main() {} which is undefined, but I cannot see why such 'features' are not deprecated so that users are properly discouraged.