[fpc-devel] weak referencing (was Suggestion:.....)
pascaldragon at googlemail.com
Mon Sep 22 14:54:31 CEST 2014
Am 22.09.2014 14:31 schrieb "Hans-Peter Diettrich" <DrDiettrich1 at aol.com>:
> Marco van de Voort schrieb:
>> (to Sven)
>> So the cycle break mechanism is going to be marking potential cycle cases
>> as weak.
>> Do you still plan to at least detect cycles for debugging purposes?
>> Or is the cycle detection itself already too hard?
>> IOW I'm wondering what will happen (and what to do) if there is a cycle
>> sufficiently complex program.
> I could imagine a tool for that purpose, instead of burdening the
compiler with such rarely used functionality. More diagnostics could be
removed from the compiler, like the detection of unused local variables or
units - if that helps to speed up compilation. Separate diagnostic tools
could immediately offer means to solve the detected problems interactively,
what's not the purpose of an compiler.
These diagnostics help the compiler to remove application code it doesn't
need to generate. So why should I remove them? Also these diagnostics are
quite fast already. Other more costly optimizations are already optional
using the -Ox options.
Additionally the cycle detection algorithm wouldn't be run at compiletime
anyway, but at runtime. Namely during every reference count decrease.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fpc-devel