 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25-10-2018 8:05, clipka wrote:
> Am 24.10.2018 um 08:40 schrieb Thomas de Groot:
>
>>> What version of POV-Ray are we talking about?
>>
>> v 3.8.0-xtokenizer.9844488+av609.msvc with Win7
>
> Ah, the experimetal new tokenizer! Now that changes things. Since we're
> talking about alpha.9861167, I had presumed that you were using at least
> some alpha as well.
Yes, it is bad practice to mix posts on different versions like I did. I
apologise.
>
>> You are right (of course you are right!): I had not yet used the alpha
>> version 3.8.0-alpha.9861167+av620.msvc14.win as I thought they were
>> more or less identical. It shows the warning for both cases indeed. I
>> had not been aware that the case had been solved in between. Thanks!
>
> Has it? I don't recall any such fix, nor it even being necessary. So
> looks like something broke during the refactoring for the tokenizer
> changes. That's conceivable.
Well, it definitely was an issue with versions 3.6 and below, and, as
far as I recall, with version 3.7.
>
> I'll investigate that once I turn my attention back to the tokenizer.
>
>
>> Phwwww..... That was close! I am glad I do not have to put myself
>> under psychiatric treatment after all ;-)
>>
>> [where are my dried frog pills...?]
>
> Probably right where I left my glasses.
That might well be the case indeed.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25-10-2018 8:39, Thomas de Groot wrote:
> Well, it definitely was an issue with versions 3.6 and below, and, as
> far as I recall, with version 3.7.
>
Just to confirm, after testing: Also an issue with version
3.7.0.msvc10.win64
The correction must have been made in one of the 3.8.0 alphas.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 26.10.2018 um 09:28 schrieb Thomas de Groot:
> On 25-10-2018 8:39, Thomas de Groot wrote:
>> Well, it definitely was an issue with versions 3.6 and below, and, as
>> far as I recall, with version 3.7.
>>
> Just to confirm, after testing: Also an issue with version
> 3.7.0.msvc10.win64
>
> The correction must have been made in one of the 3.8.0 alphas.
Having dug a bit in the revision history (my memory isn't as good as it
used to be), there has indeed been such a fix, but that was already back
in v3.7.1-alpha.8913469. Commit 3f1de0d6, dated 2016-12-11.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 26-10-2018 17:50, clipka wrote:
> Am 26.10.2018 um 09:28 schrieb Thomas de Groot:
>> On 25-10-2018 8:39, Thomas de Groot wrote:
>>> Well, it definitely was an issue with versions 3.6 and below, and, as
>>> far as I recall, with version 3.7.
>>>
>> Just to confirm, after testing: Also an issue with version
>> 3.7.0.msvc10.win64
>>
>> The correction must have been made in one of the 3.8.0 alphas.
>
> Having dug a bit in the revision history (my memory isn't as good as it
> used to be), there has indeed been such a fix, but that was already back
> in v3.7.1-alpha.8913469. Commit 3f1de0d6, dated 2016-12-11.
Ah OK. As a matter of fact, I do not have any of the 3.7.1 versions any
more... except UberPOV: 1.37.1.1-alpha.8871946.msvc14.win64, which also
shows the issue as it happens.
--
Thomas
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
