Re: problem with output of the program on different OS

On May 9, 3:11=A0pm, pereges <Brol...@[EMAIL PROTECTED]
> wrote:
> On May 9, 6:46 pm, Bart <b...@[EMAIL PROTECTED]
> wrote:
>
> > On May 9, 2:33 pm, pereges <Brol...@[EMAIL PROTECTED]
> wrote:
> > Didn't like this. I used reader(&obj); (reader takes **object).
>
> I'm sorry, you are correct.
>
> > OK, but what should the output be?
>
> > With inputs of 40000000, 0.0001 and 1100, I got:
>
> > Es: 2.979907e-012 Ei: inf RCS: 0.000000e+000
>
> > But then, I'm running on Windows and you say the problem is with
> > Linux..
>
> I will have to check up some scientific literature to determine what
> the *exact* =A0and expected output should be. But I can definetely tell
> something is wrong because I'm getting the following output on windows
> for the same input that you have taken:
>
> Es: 4.431255e-10 Ei: 1.226668e-04 RCS: 4.539517e+01
>
> There is definetely something wrong and its quite likely that these
> are all garbage values

Yes, you do have a problem. With lccwin, it gave the results I posted.
On gcc, it gave INF,INF and IND. With DMC it crashed, possibily with
pointer dereferencing (but could not pinpoint where; with debug on it
was somewhere in the runtime).

For ease of testing, I combined all modules into a single module, and
hard-coded those 3 inputs. Next (although I don't have time now) would
be output statements to pinpoint that crash, which hopefully is not
unconnected with the main problem.

It doesn't matter now what the exact results should be; get them
consistent first.

--
Bartc