mapmef@gdr.bath.ac.uk (M E Fletcher) (09/08/89)
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
ly@prism.TMC.COM (09/12/89)
QuickC 1.01 also outputs 0, 1, 2, 3, etc.
t-xiangc@microsoft.UUCP (Xiangjun Chen) (09/12/89)
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!!!
t-stevep@microsoft.UUCP (Steve Poole) (09/13/89)
In article <7668@microsoft.UUCP> t-xiangc@microsoft.UUCP (Xiangjun Chen) writes: >(Environment: > Compaq 386, MS-DOS 3.31 or OS/1 1.1 real mode) ^^^^ Gosh, and I've been limping along on its successor! -- // Use only under adult supervision. Place on ground, light fuse, // and get away. In case of ingestion induce vomiting.