Luiz,
Good work. How thread safe is your code? Tried any blob fields?
Thanks,
James
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
As I mentioned before, assuming some degree of liability for your work is on
the horizon.
From
http://www.lightbluetouchpaper.org/2007/08/10/house-of-lords-inquiry-personal-internet-security/
Quote:
"The third area, and this is where the committee has been most far-sighted,
and therefore in the
>It is supported in FPC 2.2.
Sweet!
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Daniel had mentioned your work in a community post. Thanks for the effort,
and I'd love to try it out. And thanks for that detailed post.
James
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fp
> So I don't really see the relation. Even though it may seem at first
> sight that you do not have to bother with individual objects in case
> of split heaps, in practice you do because you have to make sure that
> no pointer to any of those objects can escape beyond where you free
> the split hea
Three things needed in FPC:
1) Garbage collection. Anybody who's worked on apps with objects of objects
of objects of objects will see the value in this. If CMEM is used, can the
Boehm garbage collector be used? Even a resurrection of the split-heap stuff
into something more generalized (mini-heap
