Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!nrl-cmf!cmcl2!husc6!rutgers!mtune!whuts!homxb!houxs!daw
From: daw@houxs.UUCP (David Wolverton)
Newsgroups: comp.lang.c
Subject: Re: functions defaulting to int
Message-ID: <644@houxs.UUCP>
Date: 18 Jan 88 14:27:26 GMT
References: <528@gtx.com> <7111@brl-smoke.ARPA>
Organization: AT&T Data Systems Group, Holmdel, NJ
Lines: 15
Summary: there is a way

In article <7111@brl-smoke.ARPA>, gwyn@brl-smoke.UUCP writes:
> In article <528@gtx.com> al@gtx.UUCP (Al Filipski) writes:
> >In my opinion, one of the main design flaws in  C is the rule that
> >makes procedures int by default.
> 
> From today's point of view, yes, but before the advent of "void"
> it was quite convenient.  Of course it can't be changed now, due
> to the amount of correct existing code that would be invalidated.

Well, there is a way to change it now.  Namely, an implementation
could provide this feature (not defaulting functions to 'int') as
an option.  Of course, to be called an ANSI compiler, it would also
have to have a way to turn off this behavior.

Dave Wolverton
ihnp4!houxs!daw