Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!charon!dik
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.lang.c
Subject: Re: DEFINITE bug in Turbo C 2.0
Message-ID: <8911@boring.cwi.nl>
Date: 22 Mar 90 23:32:35 GMT
References: <802@zeusa.UUCP>
Sender: news@cwi.nl (The Daily Dross)
Organization: CWI, Amsterdam
Lines: 16

In article <802@zeusa.UUCP> hendrik@zeusa.UUCP (Hendrik Vermooten) writes:
 > Here is a definite bug in C (discovered by Renier v. Wyk)
 > 
 > (Please, no speeches about not using ++a etc in a macro :-) I've never
 >  done it, and never plan to do it. Interesting bug, nonetheless)
Right so, because it may lead to undefined behaviour.

But pray tell, what is the bug?

That undefined expressions give different results in different places?
That undefined expressions give different results with different compilers?

That is not a bug, that is a feature.
-- 
dik t. winter, cwi, amsterdam, nederland
dik@cwi.nl