|
Henrik Lindberg You bring up a good point. Count this as my official vote toward adding a protected set of classes.
I use assert_private() to ensure that users can't include classes that won't work without other parts of the module. This way I can strictly control, from the top level, how users should be using the module and it lets me logically split up my module into components.
However, I do *not* want to have to repeat all 5 million parameters at the top level, that defeats a lot of the reason that I'm splitting things off into sub-classes.
What I want is what I currently have, which I guess you could call protected, where I can control the class acesss and inclusion order and I can then allow the setting of various less-used parameters via data binding.
Alternatively, classes could be private with parameters having a flag to be public or something like that. That said, my current parameters are already going over 140 characters and I'm starting to think that .h files are about to come back into style.
|
