Re: [Chicken-users] Problem with creating extensions

[Matt Gushee]

Hi, Christian--

On Wed, Oct 16, 2013 at 12:51 PM, Christian Kellermann
<address@hidden> wrote:

> * Matt Gushee <address@hidden> [131016 19:03]:

>> If so, I think the documentation for 'require-extension' needs an
>> update. The manual states:
>>
>>   [(require-extension ID ...)] is equivalent to (require-library ID
>> ...) but performs an implicit import, if necessary.
>>
>> As I read it, that implies that placing the extension code in a module
>> is *optional*. But apparently it is now required.
>
> What would be a better explanation that would work for you?

Hopefully any changes are not just for my benefit!

But anyway ...

IF it is true that 'require-extension' now only works for code that is
in a module, then there is an obvious inaccuracy in the above
statement: 'if necessary' implies that there are some situations where
a call to 'import' is not necessary ... since that appears not to be
true any more, then just dropping 'if necessary' would fix that
sentence.

However, I think it is more important to explicitly address this issue
in the Extensions section of the Manual and/or the Eggs Tutorial. The
manual doesn't say anything about modules being required (or not), and
includes example code that apparently does not work; the tutorial just
states that you *should* use modules, for reasons unrelated to the
issue being discussed here. The reason I looked up 'require-extension'
in the first place was that I couldn't find an answer in those
obvious places.

Again, this is all assuming that modules are indeed required, and
intentionally so. Not being involved with Chicken core development, I
can't judge whether that is the case or not.

Thanks for working on this!

--
Matt Gushee