From owner-freebsd-chat Sun Sep 6 18:06:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19527 for freebsd-chat-outgoing; Sun, 6 Sep 1998 18:06:10 -0700 (PDT) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from redfish.go2net.com (redfish.go2net.com [207.178.55.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA19298 for ; Sun, 6 Sep 1998 18:05:53 -0700 (PDT) (envelope-from marcs@go2net.com) Received: from marcs by redfish.go2net.com with smtp (Exim 1.82 #2) id 0zFpit-0002aZ-00; Sun, 6 Sep 1998 18:04:03 -0700 Date: Sun, 6 Sep 1998 18:04:03 -0700 (PDT) From: Marc Slemko X-Sender: marcs@redfish To: jack cc: freebsd-chat@FreeBSD.ORG Subject: Re: Where can I find C In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 6 Sep 1998, jack wrote: > In the second edition (1988) `#include ' is part of that > listing, and it is in that brace style. However, the include > file is not required. > > germanium:jack {116} echo 'main(){printf("Hello World!\n");}' > > hello.c > germanium:jack {117} cc -o hello hello.c > germanium:jack {118} ./hello > Hello World! > germanium:jack {119} cc -v > gcc version 2.7.2.1 > > No warning, no errors, no core dumps. Just because it works on an implementation without problems or just because it was "standard" at one point does not mean that current standards allow it or that an implementation must work in that manner. So the issue is if the most relevant C standard says you need the include, then it isn't C if you don't do it even if it compiles. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message