POV-Ray : Newsgroups : povray.programming : mixing POV code with C++ : Re: POV source errors Server Time
29 Jul 2024 06:18:42 EDT (-0400)
  Re: POV source errors  
From: Ron Parker
Date: 15 Feb 1999 11:00:19
Message: <36c84493.0@news.povray.org>
On Sun, 14 Feb 1999 19:53:29 -0600, Thorsten Froehlich wrote:
>In article <36c76403.0@news.povray.org> , "Nigel Stewart" 
><nig### [at] eisanetauNOSPAM> wrote:
>
>> DBL x = 2.0;
>>
>> becomes
>>
>> DBL x = (DBL) 2.0;
>>
>> Is there anything unreasonable or dangerous about doing this?
>
>It is unreasonable: DBL x = 2.0; is c acompletly legal and *well* readable
>statement. DBL x = (DBL) 2.0 is less readable. Putting unnecessary code into
>POV-Ray just to get rid of *one* compilers warnings is _not_ reasonable.
>
>> I think it is worth keeping the MS compiler quiet, because sometimes
>> things like signed/unsigned, unused, uninitialised variable, actually
>> help solve problems.
>
>Ever considered a different compiler? ;-)

Ever run PC-Lint against POV?  I haven't tried yet, but in my experience
with real code, it's far more picky than Visual C++ is.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.