Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC840302); site log-hb.UUCP Path: utzoo!linus!decvax!mcvax!enea!log-hb!hans From: hans@log-hb.UUCP (Hans Albertsson) Newsgroups: net.lang.c Subject: K&R App A, par. 8 & 8.2, on Declarations, Defaulting. Message-ID: <180@log-hb.UUCP> Date: Sun, 24-Jun-84 11:27:56 EDT Article-I.D.: log-hb.180 Posted: Sun Jun 24 11:27:56 1984 Date-Received: Tue, 26-Jun-84 06:29:38 EDT Organization: TeleLOGIC Nyn{shamn SWEDEN Lines: 44 [] In K&R App A, para 8, it is stated declaration: decl-specifiers declarator-list(optional); and decl-specifiers: type-specifier decl-specifiers(optional); sc-specifiers decl-specifiers(optional); In para 8.2 it is stated: If the type-specifier is missing from a declaration, it is taken to be int. I interpret this to mean that a declaration MUST have either a minimum of one type-specifier, or a minimum of one sc-specifier, and, PROVIDING this condition is being met, int may be assumed, that is, all of auto a; int b; short c; register int d; register e; are acceptable, as opposed to a = 1; since there is NO specifier of any sort in the latter case. Am I right or wrong? What will ANSI say in this matter? I know that the Sargasso C for TOPS10/20 requires what I consider correct. UNIX pcc-based compilers permit the "a = 1;" form. -- {decvax,philabs}!mcvax!enea!log-hb!hans Hans Albertsson, TeleLOGIC AB Box 1001, S-14901 Nynashamn, SWEDEN