Re: It works without stdio.h !!
On Sun, 08 Mar 2009 13:14:17 -0500, Joseph M. Newcomer
<newcomer@flounder.com> wrote:
"Not defined" is not the same as being "defined to break", but it *might*. While a
compiler writer may *choose* to make an undefined program work like the 1975 PDP-11
compiler, there is no *obligation* to do so. For example, if you compile it with the
Win64 compiler, which uses a somewhat different default calling convention, it may not
work, and if you complain, the answer from the compiler writer or library writer is "I
didn't have to make it work".
What you found was one example of one compiler that does not break. The gcc folk indicate
that there is a second example of a second compiler that does not break. You may not
conclude from this that EVERY compiler will work. Nor may you assume that the next
release of a Microsoft or gcc compiler will not break.
joe
Hi Joe,
The OP crossposted this thread to comp.lang.c, and except for yours, these
replies are not coming from MFC regulars; they are coming from comp.lang.c
denizens. You've trimmed comp.lang.c from your replies, so your replies are
only going to the MFC group. This means the guy you just responded to and
perhaps the OP as well won't see your replies, and you're essentially
talking to the air. For this reason, I think there are two correct ways to
handle a crossposted thread, 1. Don't edit the newsgroup list in a first
reply, and if you do want to edit groups, set follow-ups and state what
they are, or 2. Don't reply at all. Otherwise, the thread just gets
fragmented and communication breaks down.
We both use Agent, and the option that controls this is:
: Tools/Options/Posting Messages/Composition Window/Follow-up Crosspost Action
If you set it to "Prompt for Action", Agent will ask you what to do when
you attempt to reply to a crossposted thread.
--
Doug Harrison
Visual C++ MVP