POV-Ray : Newsgroups : povray.binaries.images : unexplained : Re: unexplained Server Time
6 Oct 2024 06:23:30 EDT (-0400)
  Re: unexplained  
From: James Holsenback
Date: 16 Aug 2014 06:49:34
Message: <53ef373e@news.povray.org>
On 08/13/2014 07:28 AM, clipka wrote:
> Am 13.08.2014 12:11, schrieb James Holsenback:
>
>>>> narrowed a bit further ... this hash works fine:
>>>> 9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!
>>>>
>>>>
>>> ok so at hash 54b283a0d39c637ce9d4ab16512a364e993c58c5 its busted so I
>>> think that's considerable less territory to cover.
>>
>> this hash ac564f7231f2b05b461a3a03fe6b9ed21b845c5a is the last working
>> commit (compiles and runs OTOTest.pov properly)
>>
>> broken @ cf1c3fbedb33802bd431acac43ce41db55fa87b8 ... doesn't even
>> compile ./base/safemath.h is belching errors all over the place
>
> Ah, yes, that one... that's part of GitHub issue #29. It'll need
> replacing of "numeric_limits" with "std::numeric_limits" (and then
> probably some more fixes).

have you been able to (or are you even going to) look into why the 
implementation (re-factoring???) of this construct isn't compatible with 
my compiler (that's what appears to be happening) since you can't 
confirm on your end.

it /really/ appears that this (OTOTest file) got broken @ 
cf1c3fbedb33802bd431acac43ce41db55fa87b8 and that the issue #29 commits 
just cleaned up the implementation so i could at least compile.


Post a reply to this message

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