Iavor Diatchki wrote:
>> remove export lists, introduce public/private modifiers
> And it nicely deals with re-exporting imported entities: public
> imports get reexported, private ones don't.
note though that the public/private thing in Java
also refers to the "package" concept, which is missi
Hello,
On 2/19/06, Johannes Waldmann <[EMAIL PROTECTED]> wrote:
> > ... unless you export everything, you are forced to list all exports
> > explicitly, so there's no way to tell it just the few things you're
> > hiding (though that should not be a difficult extension).
>
> Alternative suggestion:
Cale Gibbard wrote:
> ... unless you export everything, you are forced to list all exports
> explicitly, so there's no way to tell it just the few things you're
> hiding (though that should not be a difficult extension).
Alternative suggestion:
remove export lists, introduce public/private modifi
On 17/02/06, Iavor Diatchki <[EMAIL PROTECTED]> wrote:
> The main problem I find with the module system is that it
> is difficult to export nearly everything from a module.
Just to clarify this, he means that in the sense that exporting all
but a few of the symbols from a module is difficult, not
Hello,
Do you mean the record system or the module system? I don't think
either is exactly flawed, but for both, people have wanted them to do
more (and some have suggested that they should be the same thing :-)
The main problem with the record system I have heard about is that
people want to be
Hello,
is there any web resource which describes the problems with Haskell 98's
record system in a compact form? The Curry people are about to adopt (parts
of) this module system and I warned them that many consider it flawed. Alas,
I'm not an expert in this area, so I cannot give much good a
