POV-Ray : Newsgroups : povray.general : #ifdef using a string expression? : Re: #ifdef using a string expression? Server Time
18 Apr 2024 18:55:40 EDT (-0400)
  Re: #ifdef using a string expression?  
From: William F Pokorny
Date: 18 Mar 2023 16:29:55
Message: <64161f43$1@news.povray.org>
On 3/18/23 10:19, William F Pokorny wrote:
>> To me, this would seem to be an unexpected trap, waiting to be 
>> 'exploited' by
>> mistake. I'm not sure how such a mistake might be made by a user, but 
>> still...
>>
>> My two-cents 😉
> 
> I agree with three-cents - and now we have five! 😄
> 
> I took a quick look just now and v3.7 works as expected in some quick 
> testing in that only identifiers are OK - which I do believe is the intent.
> 
> So, I'd say this is another v3.8 beta 2 bug.
> 
> It's something with the changes in parsing, but it must have happened 
> prior to Christoph's back off point for the v3.8 parser too.

Alright.

A long time ago I created a bunch of statically linked(a) versions of 
POV-Ray going back through time. Anyhow. Used these to trace the 
introduction of the str/num OK in #ifdef test bug.

Bill P.

(a) - This the old timer's container alternative.

---

commit 58d51f4911dce5e9021c62b30983902b0aab8b04  str,num OK
Author: Christoph Lipka <c-l### [at] usersnoreplygithubcom>
Date:   Sun Mar 1 02:05:39 2015 +0100

     Fixed scrambled warning messages.


// There are only five commits between the one up top and the bottom
// one below. My BIG bet is on the following commit being the problem,
// but I don't have a static compile of it or the one prior to it to
// be sure.

commit a94c1ab61aeb2aa483aa3636736ff1e24ebd8b78
Author: Christoph Lipka <c-l### [at] usersnoreplygithubcom>
Date:   Sun Mar 1 02:03:14 2015 +0100

Implemented tuple extensions to #declare and #local.
...


commit 3f56c5fb8a54998067a217e54101c799756510b4  Complains.
Author: Christoph Lipka <c-l### [at] usersnoreplygithubcom>
Date:   Tue Feb 3 16:48:11 2015 +0100

     Fixed Unix build errors.

---


Post a reply to this message

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