Re: Trouble with `export'.

[Dirk Herrmann]

On 5 Jun 2001, Rob Browning wrote:

> Dirk Herrmann <address@hidden> writes:
> 
> > We can not solve all problems with respect to binding conflicts, but
> > we should decide about a policy, like for example that conflicts
> > will result in errors.  With the possibility to selectively import
> > bindings, and in addition to rename bindings when imported, plus the
> > possibility to rename bindings when exporting them there should be
> > enough possiblilities to avoid conflicts while still being flexible.
> 
> This is true, but Marius still had a good point.  What happens if a
> module your module is already using suddenly starts exporting a symbol
> that you were already using locally?  You haven't changed your code at
> all, but now your module is broken.

Hmmm.  Yes, that's a problem.  It seems that the 'import all' paradigm
itself is broken.  You would never run into problems if you had to state
explicitly where each binding should come from.  Or, more exactly, you
still could run into conflicts, but all these conflicts should be
detectable and not happen silently.

Best regards,
Dirk Herrmann