Re: derive conflicts with multiply-defined and module level import

[S. Alexander Jacobson]

On Sat, 7 Nov 1998, Fergus Henderson wrote:
> > Well, it depends on what you call *strong*. The only reason that I heard is
> > that it prevents users from making possibly unwanted errors.
> 
> Another reason is that allowing definitions to be split up
> without any special syntax indicating this would harm readability.
> If I see a definition, I can't be sure it's complete without
> examining the whole module.

I am very sympathetic to readability arguments, but I also agree with erik
that programmers should have a way out when necessary.  Code generation is
one of those cases where one can sacrifice readability.

In that context, your proposal

> to allow them to be separated, but only
> with some special declaration, e.g. a keyword "noncontiguous",
> prefixed to each clauses, that wouldn't be so bad for readability.

Would be something that I agree with.

> But if we have to add new syntax to make it work then it
> is getting to be more trouble than its worth.

Since the application is code generation, I don't think the extra
syntax is a problem.

-Alex-
___________________________________________________________________
S. Alexander Jacobson                   i2x Media  
1-212-697-0184 voice                    1-212-697-1427 fax