In message <qq********************************@4ax.com>
Jack Klein <ja*******@spamcop.net> wrote:
On Tue, 22 Feb 2005 00:44:20 +0000, Christian Bau
<ch***********@cbau.freeserve.co.uk> wrote in comp.lang.c:
You should get a proper compiler that produces an error instead of a
warning. That is a problem with Visual C; it often allows you to compile
completely broken code and only gives a warning.
The C standard does not define "error" or "warning". It only
specifies "diagnostics" that are required in cases of syntax error or
constraint violation.
Yes, we know, but it's a quality of implementation thing, isn't it? If a
compiler doesn't distinguish between a blatantly incorrect piece of code that
violates an ISO constraint and something it thinks is just a little bit iffy,
how on earth is the average programmer supposed to know whether a "warning"
is important?
The last thing people who regard the C standard as important should be doing
is leaping to the defence of implementations like this, just to score a few
pedant points.
--
Kevin Bracey, Principal Software Engineer
Tematic Ltd Tel: +44 (0) 1223 503464
182-190 Newmarket Road Fax: +44 (0) 1728 727430
Cambridge, CB5 8HE, United Kingdom WWW:
http://www.tematic.com/