Thorsten Froehlich wrote:
> 
> Yes, this is why we would have liked to use MrC for the official version 
(and why I created the MrC makefile), but StdCLib (any version of it!) 
or MrC itself create some strange and very hard to track bugs which may
cause 
POV-Ray to crash on complex scenes (not because these are complex, 
but because of some memory copying problems, I suspect). 
As a matter of fact, the reason why this MrC compile is slower than the
last one is because 
I carefully tuned *down* the optimizations to eliminate some o
> 
> Well, for most scenes the MrC version is still useful. 
However, I would strongly recomment to run *no* other applications with
it. 
If it goes mad it will most likely damage the systems heap structures
and as the Mac has 
no memory protection (yet), other applications may suffer. 
I had to reinstall my system several times during development...
> 
> Just a warning, and the reason why we choose to the CW build.
> Note that some of the problems definetly come from the StdCLib because our CW
compile with StdClib (instead of the MSL CLib) had some problems as well.
> 

I also know MrC has a many problems,but I always use MrC in Symantec C++
8.4J.
But OS8.1 changes AppleScript,So Symantec MrC does not work anymore
except Power PCC Compiler.
PCC Compiler can not compile PNG Library but MrC can do well.

MPW 3.5d3 MrC can not recognize reduce_optimize in HFILED.C.
Recently MPW MrC can not compile HFIELD.C and System Down.

Anyway now I finish all sample scene files in Official Scenes by
UnOfficial version.

I wonder MESH TEXTURE makes new bug, I think it's cause of Ray Textures
Counter.
So I check source files.


I appriciate Mac POV Team for Appearance and Navigator makes beautiful
GUI.

Y.Tanabe

Kobe,Japan

Post a reply to this message