Re: problem with output of the program on different OS

Richard Heathfield <rjh@[EMAIL PROTECTED]
> writes:

> pereges said:
>
>> On May 8, 6:45 pm, Bart <b...@[EMAIL PROTECTED]
> wrote:
>> 
>>> Well, you can forget about the Windows version and just try some
>>> debugging! Your program clearly isn't producing the output you expect.
>> 
>> Can you please tell me about a good debugger ? Is there some
>> preliminary stuff I should read about debugging in C prior to using a
>> debugger ?
>
> Debuggers are over-rated by some people, and can be a huge time sink if 
> used flailingly.

What total and utter nonsense. When one needs a debugger they are
exceptionally useful. This constant downer you put on debuggers is more
down to your own incompetence at using one. I have never, ever had a
case where using one has cost me time or effort. At the very worst case
it can run in the bg and not actually track anything BUT still be able
to give an IMMEDIATE stack trace in the case of an exception of some
kind.

>
>>> 650 lines isn't very big, why many modules? Sometimes separating into
>>> modules can introduce more errors. Perhaps try tem****arily combining
>>> into one big file.
>> 
>> well, I have a total of 9 modules in my program(counting the .c and
>> the corresponding .h as 1 module).I was told to write the code in
>> sucha  way that the individual modules can be reused in some other
>> programs.
>
> Yes, I agree with you that the comment about design was misguided.
Module 
> boundaries should be drawn to reflect differences in functionality. The 
> idea that you have some kind of Procrustean source bed, such that any
file 
> longer than N lines must be split, is silly.
>
> Is that zip file ready yet?