> Another thing that nothing stops us from, in a late-bound programming > language without private namespaces, is adding additional methods to > base objects without changing the code that declares the base objects, > as long as the implementation of the base objects promises to remain > the same.
I do think it would be best though to come to decisions upstream to provide methods that most people will find sufficient and intuitive, because once they find it insufficient or unintuitive and add their own methods, they'll start using them in their code and the code becomes that much more forked. I find the $qp->config() style method intuitive for this myself; adding a hashref accessor to at least the notes() method and perhaps to this persistence-method-that-might-also-want-to-cover-config-needs, might be considered intuitive by many. -Jared
