Author: Robert Hyatt
Date: 08:55:06 03/06/03
Go up one level in this thread
On March 06, 2003 at 11:22:47, Vincent Diepeveen wrote: >On March 06, 2003 at 11:13:27, Robert Hyatt wrote: > >>On March 06, 2003 at 10:48:59, Vincent Diepeveen wrote: >> >>>On March 06, 2003 at 10:24:33, Michel Langeveld wrote: >>> >>>>Vince ... if u use egtb.cpp in combination with MSVC you need to set option >>>>/Zm150 to let it work. >>> >>>that's what i know of course and which bob should update in the makefile, but >>>the errors produced here are not because of that, but because of not following >>>ansi-C standards. >> >> >>Sorry but my code is 100% ansi C compliant. Feel free to point out somewhere >>where it isn't of course. >> >>Seems strange that everybody on the planet but you can compile it with no >>problems. But then again that doesn't _really_ seem so strange when I think >>about it. > >You shout out loud that the only compiler you use is intel c++ nowadays. Correct. On my linux boxes. I still use GCC to compile for our sun boxes. And our SGI boxes. And our IBM boxes. And my alpha box. > >No Hyatt, you cannot program very well at all. > a) it is not 100% ansi-C compliant and i'm not referring to the 64 bits stuff >here when compiling a multiprocessor version of crafty. Only single cpu version >goes ok by default. > Please show me where there is something that violates the ANSI-C specifications. Rather than a problem in a header file that is worked on by dozens of people and which _can_ have a broken #ifdef in it. There _is_ a difference. >Somehow i get the impression your software gets more and more outdated each >month... > >Best wishes debugging, >Vincent Fortunately I have programmed long enough that bugs are not that common. You should try that sometime.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.