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: 761 bytes --]

"Hibou57 (Yannick Duch�ne)" <yannick_duchene@yahoo.fr> wrote in message 
news:3084820f-4799-4555-b309-92c8ff7e2436@m16g2000yqc.googlegroups.com...
...
> Using such redundancies sometime, in the opposite, help
> readability or is useful when it recall something explicitly, but
> sometime, when it is too much, it breaks readability and comes with a
> feeling of confusion.

Surely I have a feeling of confusion :-) at the idea of having a generic 
package with a large number of interelated formal packages. That sounds a 
new way to create unmaintainable spagetti code (gotos aren't the only way to 
make things impossible to understand). That's irrespective of how the 
formals on the outer package are named.

                                   Randy.