[fpc-devel] Initialize/Finalize management operators and Default intrinsic
Maciej Izak
hnb.code at gmail.com
Tue Apr 12 14:58:05 CEST 2016
2016-04-12 14:33 GMT+02:00 Sven Barth <pascaldragon at googlemail.com>:
> [Note: this is less a "I don't want it", but a "I don't like it"]
>
> phew!
> > Note: these attributes are on my TODO list.
>
> Please don't do anything attribute related until I've merged Joost's class
> attributes branch which lays the foundations for the attributes. I've
> planned this for after the reintegration of my dynamic packages branch
> which is currently WIP (the merge, not the branch ;) )
>
IIRC the branch is incomplete (for example RTTI in early stage and for
example TValue need to be improved). Extending these branch is also on my
TODO. :) Maybe the only target of mentioned branch is to allow attributes
of classes (which has no much sense without Invoke method and extended RTTI
- and that is absolutely unimplemented).
> That together with your suggestion to force this attribute for records
> with management operators might indeed be useful, but there are some
> problems... (see below)
>
> > ...
>
> The system unit's initialization *must* be run first, otherwise you won't
> have a heap or synchronisation primitives or whatever you might need. That
> then also extends to units like heaptrc, cmem, cthreads, etc.
>
> Maybe it would be better to initialize such records always *after* *all*
> initialization sections have been run... :/ (and deinitialized first)
>
Maybe "run" for my idea is a bad word. We don't need to run any section
before initialization section from system. What we need is the table/list
with "fixed" variables which needs to be initialized in system.pp
initialization (and finalized in finalization). I think that is doable.
--
Best regards,
Maciej Izak
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freepascal.org/pipermail/fpc-devel/attachments/20160412/2f82ba63/attachment.html>
More information about the fpc-devel
mailing list