Re: when to call provide, first or last?

[Le Wang <l26wang@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

On Mon, Feb 27, 2012 at 9:35 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:

> Actually, such mutual dependencies aren't desirable


Can you elaborate on this a little?  In my mind if two files implement
different parts of the same libraby, it's quite natural for mutual
dependencies to occur.


> : sometimes they're
> hard to avoid so we prefer to live with them, but that doesn't change
> the fact that they're not good.
>
> Putting the provide at the end makes sure that if featurep says t, then
> it means thatthe feature is actually available, whereas if it's at the
> beginning, featurep returning t only mean "we've started to lead the
> feature, and well, maybe we've actually loaded it all by now, but I'm
> not sure".
>
> The difference is sufficiently unimportant to deserve bikeshedding,
>

cool word -> bikeshedding


> I guess, but in any case, the convention is to put it at the end.
> Like every convention, there can be exceptional circumstances that
> justify doing it differently, but they have to be exceptional rather
> than only based on taste.
>
>
>        Stefan
>



-- 
Le

[-- Attachment #2: Type: text/html, Size: 1825 bytes --]