[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] [PATCH] Fix #1506 by detecting import of module be
From: |
elf |
Subject: |
Re: [Chicken-hackers] [PATCH] Fix #1506 by detecting import of module being defined |
Date: |
Sun, 07 Apr 2019 09:24:03 +0000 |
Ah, got it. My apologies. (Only starting to look at the module code now.)
-elf
On April 7, 2019 7:57:37 AM UTC, Peter Bex <address@hidden> wrote:
>On Sun, Apr 07, 2019 at 04:05:53AM +0000, elf wrote:
>> Question: does it handle circular imports? Is
>> module a -> import b
>> module b -> import a
>> an error? Should it be?
>
>AFAIK this isn't possible because you can't import modules
>that the compiler doesn't know about. So when a imports b,
>you will get a message that b does not exist (yet).
>
>The issue with a module importing itself was that the module
>is registered as soon as the (module foo ...) is seen, which
>meant it was able to import itself.
>
>Cheers,
>Peter