Re: Trouble with `export'.

[Rob Browning]

Marius Vollmer <address@hidden> writes:

> will put the wrong variable into the public interface of mod2.  This
> happens since `export' can not know whether there will be a local
> definition for a name later on.

Couldn't define check for this and issue a warning?  Presuming I
understand the situation, it seems like it could be considered an
error condition.  In this situation, aren't you defining a binding
that as far as the local module is concerned, already exists?

set! should be ok, but it seems like maybe define should balk.

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930