Anon, thanks for the response. The main problem I'm trying to solve is that I have two classes of data (pardon the pun). I have some data and methods that are fairly static, those are going into the main package file. Then I have some data that is more variable, which I want to have in a separate file (and I mean file in the literal sense here) so that it can be more easily be regenerated. In my (admittedly naive) view, it seems that a subclass would be a good way to handle that, but I am definitely open to other suggestions.
In regards to not allowing direct access to fields, that's what I'm working on, or trying to at least. :) What I'm trying to figure out is what's the best way to go about that. I like the idea that Athanasius floated about "hiding" the static data in private variables, and creating methods in the subclass that do the work I'm currently doing in the main package that needs that data. If I understand what you're saying correctly, that seems to be what you're proposing as well?
Honestly, I don't understand your third paragraph, but hopefully what I've said above clarifies why I think I need a subclass.
The solution of the fourth paragraph muddies the water between the static and the dynamic data, that I described above. And thanks for the tip on Exporter, apparently I was too liberal with my copy and paste.
In reply to Re^2: OO manner of accessing static variables in a subclass?
by HipDeep
in thread OO manner of accessing static variables in a subclass?
by HipDeep
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |