 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi folks,
this is a heads-up for all of you who are faithfully working on
derivatives of POV-Ray - be it qtpovray, the mac port, or what-have-you.
We're currently preparing to enter the beta phase of POV-Ray v3.8;
however, in order to do so, we will _not_ continue from the current
master, but rather back up a bit, to the last commit before we
integrated the overhauled tokenizer/scanner into the parser. To help you
more easily find that commit in question (85db57d9), we've tagged it as:
`nexus-v3.8-v4.0`
Also, v3.8 development will _not_ continue in the `master` branch, but
rather a dedicated branch, `release/v3.8.0` (which already exists and is
currently ahead of The Nexus, but will be backed up and branch off soon).
Note that besides reverting to the old parser, this will also revert
back to the use of the boost-thread and boost-system libraries.
We recommend that you _do_ keep all the work you've done since The
Nexus, as the current state of v3.8 will live on under the moniker v4.0.
There's nothing fundamentally wrong with the changes we introduced since
The Nexus - we just won't be able to get them to a clean state as fast
as we'd like to, and we'd probably have to break backward compatibility
more than we'd be comfortable with in a v3.x release.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Hi folks,
>
> this is a heads-up for all of you who are faithfully working on
> derivatives of POV-Ray - be it qtpovray, the mac port, or what-have-you.
>
> We're currently preparing to enter the beta phase of POV-Ray v3.8;
> however, in order to do so, we will _not_ continue from the current
> master, but rather back up a bit, to the last commit before we
> integrated the overhauled tokenizer/scanner into the parser. To help you
> more easily find that commit in question (85db57d9), we've tagged it as:
>
> `nexus-v3.8-v4.0`
>
> Also, v3.8 development will _not_ continue in the `master` branch, but
> rather a dedicated branch, `release/v3.8.0` (which already exists and is
> currently ahead of The Nexus, but will be backed up and branch off soon).
>
> Note that besides reverting to the old parser, this will also revert
> back to the use of the boost-thread and boost-system libraries.
>
>
> We recommend that you _do_ keep all the work you've done since The
> Nexus, as the current state of v3.8 will live on under the moniker v4.0.
>
> There's nothing fundamentally wrong with the changes we introduced since
> The Nexus - we just won't be able to get them to a clean state as fast
> as we'd like to, and we'd probably have to break backward compatibility
> more than we'd be comfortable with in a v3.x release.
That sounds reasonable, thanks !
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 6/10/2021 5:47 AM, clipka wrote:
> Hi folks,
>
> this is a heads-up for all of you who are faithfully working on
> derivatives of POV-Ray - be it qtpovray, the mac port, or what-have-you.
>
> We're currently preparing to enter the beta phase of POV-Ray v3.8;
> however, in order to do so, we will _not_ continue from the current
> master, but rather back up a bit, to the last commit before we
> integrated the overhauled tokenizer/scanner into the parser. To help you
> more easily find that commit in question (85db57d9), we've tagged it as:
>
Bleh. I'll bet this breaks my SDL debugger
( https://www.buckosoft.com/qtpovray/debugger.html )
which was a really simple hook into the new parser.
--
dik
Rendered 50,081,587,200 of 50,081,587,200 pixels (100%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 25.06.2021 um 20:59 schrieb Dick Balaska:
> Bleh. I'll bet this breaks my SDL debugger
> ( https://www.buckosoft.com/qtpovray/debugger.html )
> which was a really simple hook into the new parser.
I take that as a compliment to the new parser's internal architecture.
Don't worry - once v3.8.0 is out, and work starts for good on its
successor, the new parser will definitely be back on board.
(I'm tempted to try and work the new parser into a v3.8.1, but that may
not necessarily happen. It all depends on how backward compatible I can
make it behave.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
