Sign in Join

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

Mailing lists / fpc-devel / 2007-04

Wish for merging back fixes

3 messages · 3 people ·

Reply by email Subscribe to this list Your subscription

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

Martin Schreiber

Hi,
Now that it is clear that FPC 2.2 can not be used with MSEide+MSEgui because of Mantis 8481 ("By copying an record with OLE string fields, the memory location of the *source* string is changed."), I would be happy if the fixes for Mantis 8103, 8245, 8386 and 8388 could be merged back to fixes_2_0 in order that we don't need to patch it anymore.

Thanks a lot!

Martin

Reply by email

Florian Klaempfl
to Martin Schreiber
Hi, Now that it is clear that FPC 2.2 can not be used with MSEide+MSEgui because of Mantis 8481 ("By copying an record with OLE string fields, the memory location of the *source* string is changed."),

The old behaviour regarding this was simply buggy. You could have ended with a non copied olestring.

I would be happy if the fixes for Mantis 8103, 8245, 8386 and 8388 could be merged back to fixes_2_0 in order that we don't need to patch it anymore.

For us, 2.0 is closed but I guess you can get write access to it if you want to merge patches.

Reply by email

Peter Vreman
to Martin Schreiber: Now that it is clear that FPC 2.2 can not be used with MSEide+MSEgui because of Mantis…
you wrote 6 lines
Hi, Now that it is clear that FPC 2.2 can not be used with MSEide+MSEgui because of Mantis 8481 ("By copying an record with OLE string fields, the memory location of the *source* string is changed."), I would be happy if the fixes for Mantis 8103, 8245, 8386 and 8388 could be merged back to fixes_2_0 in order that we don't need to patch it anymore.

Sorry, but that is not a good argument for asking merges. Depending on compiler/rtl internals is a bad design. Merging those revisions will not help in the long future either if everyone is using 2.2.x+ except MSE because it depends on 2.0.x internals.

Peter

Reply by email