If you can't foresee any other implementing classes, ignore it. And hope your foresight is correct. :)
On Tue, 3 Dec 2002, James Stauffer wrote: > Is it good to have an interface if there will only be one class to implement > it in the foreseeable future? Does it add unnecessary complexity? It usually > isn't much more complex but does that extra complexity add extra value? > Agile programming seems to say "don't build it because you won't need it." > What do you think? > > James Stauffer > > > > ____________________________________________________ > To change your JDJList options, please visit: > http://www.sys-con.com/java/list.cfm > > Be respectful! Clean up your posts before replying > ____________________________________________________ > --------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
