can we detect at compile time module ctor/dtor cycles ?

[Timothee Cour]

On Mon, Jun 17, 2013 at 5:11 PM, bearophile <bearophileHUGS at lycos.com>wrote:

> Andrej Mitrovic:
>
>
>  No idea, but I've wondered this myself too. After all "imports" are a
>> static feature and all are known at compile-time.
>>
>
> rdmd is used often in a situation where it knows all the modules of a
> program. So it must be able to detect those cycles. It seems an enhancement
> request for rdmd. Maybe a similar enhancement is possible for dmd, because
> there are plans to make the D compiler able to find all the modules it
> needs to compile a program.
>
> Bye,
> bearophile
>

why do the email threads keep splitting up again?
Anyways, on the original thread 'can we detect at compile time module
ctor/dtor cycles ?', Steven Schveighoffer raised the concern that di files
may have certain private imports not written in the di file, to which I
answered we can at least attempt cycle detection at compile time (which
won't catch all cases) followed by cycle detection at runtime.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d-learn/attachments/20130617/2cf87857/attachment.html>