In article <web.3ffc64d3e05b701c9fd50ea0@news.povray.org> , "JenniferJ" 
<nomail@nomail> wrote:

> The 3.5 version for Windows couldn't be compiled by VC.NET. Is there a plan
> on supporting it?

No, POV-Ray will forever use an outdated compiler on Windows.  Also, you
should have mentioned that you are talking about Visual C 7.1, because that
is the compiler/library combination with problems, not VC 7.0.

> 2. all other changes are related to compile-time errors from math functions.
> VC.NET is more restrict on syntax, so it issues errors for pow(2,2). It
> should be pow((double)2,2). pow() is one of the math functions, there're
> also sqrt(),fabs...

This is not as trivial as this.  And putting a cast in front of a constant
is just the plain wrong way of solving this.  In fact, if used without care,
casts will create unnecessary performance bottlenecks.  Blindly doing
whatever is necessary to please a broken compiler/library combination is no
good idea!

The problem is that in VC 7.1 many bugs and most of VCs non-standard
behavior was corrected compared to early versions of VC.  However, the C
libraries that come with VC 7.1 are still pretty much the same junk that
already came with VC 6.0.  So, now you have a conforming compiler and non
standard conforming libraries, which results in compilation problems in
standard conforming code...

Good compilers like Intel's, if provided with a conforming C library will
not exhibit any problem.  Nor will any other serious compiler around.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message