Would you approve something like this, Jonas? I admit it's not properly
tested yet, but I'm descending from TLinkedListItem (and the descendant
class can itself be descended from) and the TAOptObj class handles
allocation and cleanup of extra information. I'm not sure how practical
it is, but
That seems fair - thanks for the advice Jonas. Now I just have to
decide where best to store this linked list of records. I'm sensing the
best place would be the TAsmOptimizer object that gets created and
released with each procedure that's optimised, if I remember correctly.
Gareth aka. Kit
On 03/10/2021 23:32, J. Gareth Moreton via fpc-devel wrote:
> One drawback I've noticed is that there's no clean way to free the
> optinfo pointer when the tai object is destroyed,
The best way to handle this is by allocating the optinfo's from a pool
(linked list of more or less arrays of whateve
