Hi, sorry for the late response - but currently I'm more away than in the office...
So, although I think you already did the changes (which is OK), yes, the changes should do no harm and making things final is a good idea. Carsten > -----Original Message----- > From: Peter Donald [mailto:[EMAIL PROTECTED]] > Sent: Sunday, July 07, 2002 9:00 AM > To: [EMAIL PROTECTED] > Subject: XML Utilities > > > Hi Carsten (and other Cocooners), > > I have just been playing around with the XML stuff. I notice that a bunch > of classes have protected variables. As these can make system evolution > difficult to do while remaining backwards compatible I would like > to remove > these. > > I made the variable in XercesParser private as I figured that > there was no > real way you could subclass XercesParser and reuse the variable. > However I > held off doing the same for any of the other classes as they could > conceivably be used by subclasses. Thus I am not sure if changing them > would break any code. I suspect not but I figured I would ask you first. > Would there be any probalem with making the variables private and > potentially of making classes final? > > > Cheers, > > Peter Donald > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > "Faced with the choice between changing one's mind, > and proving that there is no need to do so - almost > everyone gets busy on the proof." > - John Kenneth Galbraith > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
