Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!microsoft!t-xiangc
From: t-xiangc@microsoft.UUCP (Xiangjun Chen)
Newsgroups: comp.lang.c
Subject: Re: Bug in Microsoft 5.1 C
Message-ID: <7668@microsoft.UUCP>
Date: 11 Sep 89 21:08:18 GMT
References: <1989Sep8.102916.16667@gdt.bath.ac.uk>
Reply-To: t-xiangc@microsoft.UUCP (Xiangjun Chen)
Distribution: comp.lang.c
Organization: Microsoft Corp., Redmond WA
Lines: 24

In article <1989Sep8.102916.16667@gdt.bath.ac.uk> mapmef@gdr.bath.ac.uk (M E Fletcher) writes:
>Thank you to everyone who tried to help with my bug. I have since
>found out that the bug only occurs if I produce an executable file
>using the QuickC package. If I use the normal cl compiler then it
>works fine. So there definately seems to be a bug in QuickC.
>
>Matthew Fletcher, University of Bath, England

As you said "there definetely seems to be a bug in QuickC" and it was mentioned
to be a bug in Microsof 5.1 C, I assume you got this problem when you use C 5.1
with the switch -qc.
So I tried to compile both of your examples in the way I assumed above, they
both works fine.

I also tried to compile the two example with QuickC 1.01, and it works fine
too.

(Environment:
   Compaq 386, MS-DOS 3.31 or OS/1 1.1 real mode)

So can you specify what version of Quick C you used in your examples and
what is the environment you produced the bug?  Let bag the bug!!!