On Friday 26 September 2003 07:41 am, Kip Hampton wrote: > > But I do worry slightly that this is the thin end of the wedge... So we > > should either make sure the AVT function is fully exposed so other > > taglibs can (ab)use it, or decide now it should remain private. > > Hmmm... I can certianly see where providing access to the AVT behavior > could be helpful/useful to taglibrarians. OTOH, the more we bolt on to > the current XSP.pm, the harder we make it to refactor later without > breaking back-compat (and it *will* be refactored, my friend, oh, yes. > and with extreme prejudice :-). I cast a tenative vote for "make it > public". Other thoughts?
-1 to making it public, at least for now. I think adding AVT functionality for the name attribute is a good stop-gap measure, helping to clean up code, but if there's no guarentee this sort of functionality would be available in a refactored XSP, then making it public "just because we can" doesn't sound like much of a code-maintainer's paradise. -- /* Michael A. Nachbaur <[EMAIL PROTECTED]> * http://nachbaur.com/pgpkey.asc */ "Oh no, not again."
