Christoph Lipka

Those files date back to a time when C++11 was still a new thing, and POV-Ray tried to avoid requiring it, to be compatible with older compilers. We simply haven't...

For the records: As this applies to an exotic platform, we probably don't want to tackle it in the upcoming v3.8.0 release. It does limit the set of compatible platforms...

For the records: Given the state of this issue, I presume we don't consider it important enough to address in v3.8.0.

For the records: As a long-standing bug, this is probably not something we want to tackle in a hurry while we prepare for v3.8.0 release.

Does someone have the time to compile a TL;DR of what problems still remain, as well as what porposals exist to fix them, and plonk this report into a new...

For the records: I consider this a precision issue that we don't want to tackle in a hurry while we prepare for v3.8.0 release.

I see no reason to pull the `brilliance on|off` switch out of v3.8; however, we should document it properly before doing the v3.8.0 release.

For the records: Since it has been decided that v3.8 won't see any further cleanup of character encoding related stuff, it makes no sense to put this one on our...

Technically, this issue is fixed in v3.8.0, to be released in v3.8.0-beta.2. However, the bug has highlighted the shortcomings of the current design, in that the typical use cases for...

While a lot of this may have been done already, this is certainly something we want to look over again before we release v3.8.0.