Path: utzoo!mnetor!spectrix!yunexus!maccs!gordan
From: gordan@maccs.UUCP (gordan)
Newsgroups: comp.lang.c
Subject: Re: The D Programming Language (was: Still more new operators)
Message-ID: <1020@maccs.UUCP>
Date: 27 Feb 88 04:12:29 GMT
References: <11702@brl-adm.ARPA> <243@eagle_snax.UUCP> <2245@geac.UUCP> <2718@mmintl.UUCP> <1988Feb25.202237.8688@utzoo.uucp>
Organization: Worldwide Phlogiston Cartel
Lines: 26

-> ... An undeclared variable should be an error, not an int.
-
- [various flames stating that an undeclared variable *is* an error]


Perhaps what the original poster meant by his statement was that, for
instance, the following is legal:

  foo (a, b)
  char a;     /* b is implicitly an int */
  {
   ...
  }

(Chapter and verse:  K & R, Appendix A, Section 10.1, "Any identifiers
whose type is not given are taken to be _int_.").

Of course, in the above example, 'b' is not a variable, but a formal
parameter.  Still, this is a problem... I once had a hard-to-find bug
that resulted from a missing formal parameter declaration defaulting to
int.  _Has_ this been changed in ANSI C?
-- 
I am the Lizard King    "Vous cherchez Jim, Monsieur?"
and I can do anything
                          -- caretaker at                Gordan Palameta
 -- Jim Morrison             Pere Lachaise      mnetor!lsuc!maccs!gordan