Re: problem with output of the program on different OS

On 12 May, 02:35, Richard Heathfield <r...@[EMAIL PROTECTED]
> wrote:
> Richard Heathfield said:
> The remaining
> warnings are:
>
> reader.c:68: warning: passing arg 2 of `calloc' as unsigned due to
> prototype
> reader.c:69: warning: passing arg 2 of `calloc' as unsigned due to
> prototype
> reader.c:109: warning: enumeration value `LAST_LINE' not handled in
switch
>
> Although I don't like the first two, I can live with them if you can -
the
> alternative (i.e. to use unsigned types for nvert and ntri) may be more
> painful to fix than is practical (I haven't delved).
>
> The last one, I leave in your hands. I'm not making any huge attempt to
> understand the program here - I'm just looking at the C.

I believe the last warning is not a problem , the LAST_LINE
thing is the condition of the while loop.

> I needed to C90ify the test.c file, changing a comment to /* style */
and
> moving a definition up a bit. The reflection.c file also needed some
> comment-fixing.
>
> Now it compiles. It doesn't /link/, but that's my makefile's problem,
not
> yours.

You wrote a makefile for such a simple project ?
I just did (on Linux) cc -Wall *.c -lm

> So let's run it:
>
> $ ./raytrace
> Enter the frequency of the electromagnetic rays to be fired
>
> Well, I have no idea what to type here...

But elsethread the OP specifies which values you
should enter for all the questions.

> ...so I just entered 0 for everything,
> and lo and behold, I got an assertion failure:
>
> raytrace: radar.c:49: gen_grid_points: Assertion `numpointsx > 1'
failed.
>
> I added this assertion because your code assumed that numpointsx could
not
> be 1 or lower. That assumption is clearly wrong.
>
> I suggest you fix this (by validating your data before passing it to the
> function that needs it to be > 1). If the code continues to give
problems
> after that's fixed, show us the fixed code so that we know that this
> particular problem is known not to be a candidate any longer.