|
 |
On 5/28/21 9:41 PM, Bald Eagle wrote:
> "Tor Olav Kristensen" <tor### [at] TOBEREMOVEDgmail com> wrote:
>
>> To fix this I would prefer to change the order of the "ifs" in the
>> OrthogonalVector() macro.
>>
>> If the old VPerp_To_Vector() macro is changed to call (wrap) the new
>> OrthogonalVector() with reordered "ifs", it will break scenes using the
>> VPerp_To_Vector() macro.
>>
>> So now I'm not sure what to do...
>
> 2 things here:
>
> 1. I may be wrong, but I was under the impression that povr is a fork, and it's
> purpose is to improve and fix some longstanding issues with the official povray
> source code. So breaking older scenes is probably not the primary concern.
Yes, the povr branch breaks what it needs to break to fix longstanding
issues - and to evolve more radically(1). It's a big part of the aim of
of it. So yep, the change likely doesn't matter even if it does break
something...
(1) - So I can try more of what I want to try... :-)
>
> 2. I thought that this was what the #version directive was for. Can't you
> sniff the scene version and include a fork in the wrapper? If the version is
> old, use the old way, and if it's new, use the new way?
I suppose, but I'm trying to avoid as much of that sort of thing as
possible with povr. I've been ripping out backward compatibility stuff
as I can for a long time now and there is still lots of it in there...
Rambling. At a high level I think about the ever backward comparability
in POV-Ray proper and it's kind of amazing it's been kept up. I mean it
all more or less works! For what I'm doing it's just not possible in
many cases - hammer in hand, I'm breaking stuff.
Bill P.
Post a reply to this message
|
|
