[m-dev.] Module qualification of typeclass methods

Simon Taylor stayl at cs.mu.OZ.AU
Fri Nov 23 07:04:22 AEDT 2001


On 23-Nov-2001, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> On 23-Nov-2001, Simon Taylor <stayl at cs.mu.OZ.AU> wrote:
> > On 23-Nov-2001, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > > Anyway, even if this example was serious problem,
> > > is `:- auto_import' going to solve it?
> > > The user of the package is at the mercy of the package designer.
> > > If the package designer didn't factor the modules well in the first place,
> > > what makes you think they're going to use `:- auto_import' well?
> > 
> > In this case it's not the package designer using `:- auto_import',
> > it's the .NET interface generation tool.
> 
> Exactly my point -- how is this automatic tool going to know which
> `:- auto_import' declarations to use?

It knows to use a `:- auto_import' declaration for the small module
introduced for each class.

Simon.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------



More information about the developers mailing list