Re: Generic package parameters not externally visible : what's the rational ?

["Randy Brukardt" <randy@rrsoftware.com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

"Hibou57 (Yannick Duch�ne)" <yannick_duchene@yahoo.fr> wrote in message 
news:b6d32b60-333f-495d-b17a-7ab589690bbb@d10g2000yqh.googlegroups.com...

...
>But right a few minutes ago, I was thinking that is may be finally
>better to be able to hide something there. Perhaps peoples who were
>talking about protecting type privacy, were thinking about a formal
>parameter used in the private part of the package only. When it is
>(this may not always be so much strange as it seems, to give formals
>parameters which are only used in private part), it is better to not
>make these visible from the outside. Providing this is a good answer,
>then the actual is so just the best, because it allow to show or hide
>at the discretion of the author (the language does not impose anything
>there, except it hides by default, and that's finally a good fact).

By jove, I think he's got it! :-)

The above reasoning makes sense, and it actually seems to reflect the 
supposed rationale. It would be nice if a fuller example of this was 
included somewhere. (I'd put it into the AARM if I had any idea of where it 
should go.)

                                             Randy.