I share some results of my quest for a uniform memory management model across all platforms. For some reason, it also touches on old-school linked lists and new-school messaging...

-
I share some results of my quest for a uniform memory management model across all platforms. For some reason, it also touches on old-school linked lists and new-school messaging...
https://blog.grijjy.com/2017/08/09/experiments-in-uniform-memory-management/

Comments

  1. Jeroen Wiert PluimersAugust 9, 2017 at 11:04 AM

    Interfaces seems the way to go.

    ReplyDelete
  2. T n T (Kryvich)August 9, 2017 at 11:12 AM

    So much overhead just to not write "Free" in the code...
    (I'm about automatic MM at all).

    ReplyDelete
  3. A. BouchezAugust 9, 2017 at 11:04 PM

    Agree with the content... Couldn't have say better the concerns with multiple memory management in Delphi, and breaking changes. This is in fact why I use now FPC for server work, which has perfect Linux support.

    ReplyDelete
  4. David HeffernanAugust 9, 2017 at 11:05 PM

    If only Emba had simply never introduced ARC we would have a uniform model.

    ReplyDelete
  5. Stefan GlienkeAugust 10, 2017 at 7:09 AM

    David Heffernan We still would have two different ones which developer are fighting since Delphi 3 (I am assuming you mean ARC for objects).

    ReplyDelete
  6. David HeffernanAugust 10, 2017 at 7:42 AM

    Stefan Glienke Yes, I meant ARC for objects.

    ReplyDelete
  7. Lars FosdalAugust 11, 2017 at 4:38 AM

    Having two memory life cycle models is lunacy. I can understand that some people don't want ARC for old school code, but there should be an option to run full ARC for VCL/RTL for Windows too. I would gladly spend time on porting our old model to ARC.

    ReplyDelete

Post a Comment