We should think about this from the client's perspective. Clients generally don't care how big the underlying implementation is. What they care about is having a meaningful API to call. If we start changing the client API simply because we think the implementation is getting too big, well, then I think we have bigger problems... ;-)
-- Martin Cooper On Tue, 27 Jul 2004 17:20:07 -0400, Gary Gregory <[EMAIL PROTECTED]> wrote: > Hi there, > > ArrayUtils is currently a 3800+ line monster file. I am working on > adding "add" and "addAll" methods for 2.1 and am wondering what folks > would think of a separate class for these ops: ArrayAddUtils? > AddArrayUtils? > > Thanks, > Gary > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
