Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!munnari!otc!mikem
From: mikem@otc.OZ (Mike Mowbray)
Newsgroups: comp.lang.c++
Subject: Re: Cornell V1.2 Bug Report (1/5)
Message-ID: <119@otc.OZ>
Date: Fri, 8-May-87 21:04:47 EDT
Article-I.D.: otc.119
Posted: Fri May  8 21:04:47 1987
Date-Received: Sun, 10-May-87 02:59:22 EDT
References: <909@batcomputer.tn.cornell.edu>
Distribution: world
Organization: O.T.C. Systems Development, Australia
Lines: 20

in article <909@batcomputer.tn.cornell.edu>, gdykes@batcomputer.tn.cornell.edu (Gene Dykes) says:

> [ ... ] if I declare a function "void func(float)" and then call it
> with an integer I want an error reported - I don't want C++ to coerce
> the int into a float for me.  Wouldn't it be a good idea to have
> something like "#define CC_STRICT" that would optionally turn off this
> kind of type conversion?

I too would like to have the option to turn on such warnings, especially 
in the case of user-defined types. Sometimes the coercion will NOT be
what you want.

My preference, though, would be for a command-line option to CC, rather
than a #define.

			Mike Mowbray
			Systems Development
			Overseas Telecommunications Commission (Australia)

UUCP:   {seismo,mcvax}!otc.oz!mikem              ACSnet: mikem@otc.oz