Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2013-11

TBookmark Type Change Status Request

3 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Tony Whyman

Does anyone have an update on which release the TBookmark type change from pointer to TBytes is going to be rolled out? I have heard that it will not now be in 2.6.4.

It's not that I want to use this change, I just want to set a sensible (and stable) bit of conditional code to cope with the change.

Tony Whyman
MWA Software

LacaK
to Tony Whyman

AFAIS this change is not merged to FPC 2.6.3, so I think, that it will NOT be a part of 2.6.4
L.

Show quoted text 14 lines
Does anyone have an update on which release the TBookmark type change from pointer to TBytes is going to be rolled out? I have heard that it will not now be in 2.6.4. It's not that I want to use this change, I just want to set a sensible (and stable) bit of conditional code to cope with the change. Tony Whyman MWA Software _______________________________________________ fpc-pascal maillist - http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Marco van de Voort
to Tony Whyman: Does anyone have an update on which release the TBookmark type change from pointer to…

In our previous episode, Tony Whyman said:

Does anyone have an update on which release the TBookmark type change from pointer to TBytes is going to be rolled out? I have heard that it will not now be in 2.6.4.

That is correct. I see now that the deprecated message in the source was never corrected. The decision was made quite some time ago, and partially also because there was a lot more involved than I initially thought.

The same division line will also change the buffer type to Pbyte. This can already be abstracted by using TRecordBuffer as much as possible.

It's not that I want to use this change, I just want to set a sensible (and stable) bit of conditional code to cope with the change.

2.7.0 (2.7.x) is the safe version to make the break. The change happened in trunk long ago, and anything newer will get a higher number.