An object based container library would also be helpful.
With classes stored on the heap you always need additional memory
access. Just one, but that is already bad in performance critical loops
Best, Benito
Am 06.06.19 um 18:23 schrieb George Bakhtadze:
It would be also great if there was an official set of interfaces (not
necessarily in interface type form but API description) describing all
these generic containers and algorithms.
Thus, all implementations which follow these interfaces are
interchangeable.
I believe this is even more important than 4-th or 5-th implementation.
---
Best regards, George
06.06.2019, 17:58, "Ben Grasset" <operato...@gmail.com>:
On Wed, Jun 5, 2019 at 11:11 AM Sven Barth via fpc-devel
<fpc-devel@lists.freepascal.org
<mailto:fpc-devel@lists.freepascal.org>> wrote:
You could try to adjust the FGL unit to use the pluggable
sorting system introduced here:
https://svn.freepascal.org/cgi-bin/viewvc.cgi?view=revision&revision=41167
Wouldn't that system itself need to be generic and not just use
void pointers first? Or is that part of what you meant?
IMO something FGL would benefit from also is the removal of the
probably-not-the-best-design inheritance from non-generic TFPSList
to everything else, which prevents inlining in a large number of
places (the compiler notes indicating such are visible basically
any time you use anything from FGL.)
,
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
<mailto:fpc-devel@lists.freepascal.org>
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist -fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
