han@uxe.cso.uiuc.edu (09/12/88)
Does anyone have a bug list for Microsoft QuickC?
I have been having problems with a not-well-organized
program I wrote.
First, the program would just stop without any reason
and hangs the computer. I didn't solve the problem
but found out a way to get around it. I replaced the
call of the inner most level function with
the whole body text of that function and voila, it
worked fine.
Qn: Is there a limitation on the number of levels
of functions that can be called? (not recursive)
My program has the most 5 - 6 levels. (no recursions)
Second, I have had problem with 'fopen' and 'fprintf'
to files also. My codes are something like the following:
FILE *f1, *f2, *f3;
...
f1 = fopen (file1, "a");
f2 = fopen (file2, "a");
f3 = fopen (file3, "a");
...
fprintf (f1, "%s%s%s", strg1, strg2, strg3);
...
fprintf (f2, "%s%s%s", strg1, strg2, strg3);
...
fprintf (f3, "%s%s%s", strg1, strg2, strg3);
...
The program executed to the end and a check with the debugger
showed that at some points, all the above statements were
executed. When the program terminates, although all 3
files were created, file3 has null data in it, even though
'fprintf (f3, "%s..."' was executed. I tried a two file version
also, ie. dealing only with f1 and f2, and file2 was empty that
time. I also increased the number of FILES=num in CONFIG.SYS
and rebooted the PC and tried it but got no improvement.
Again, I didn't solve the problem but got around it. I blocked
each set of codes pertaining to each file like
{
FILE *f1;
...
f1 = fopen (file1, "a");
fprintf (f1, ...);
...
}
{
FILE *f2;
...
f2 = fopen (file2, "a");
fprintf (f2, ...);
...
}
...
and it worked!
I am new to QuickC. I compiled my program with QCL with -AM option
and linked with the linker LINK with MLIBC7 library and nothing else
(didn't know what else was needed). I am using an IBM PS/2 Model 60
computer.
Any help will be greatly appreciated.
han...