why overload return type for thread safe and non thread
safe types ? it may cause callers' misuse and handling
overhead.

why not simply use two api for this purpose ?


>From: John McNally <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>Subject: Re: Vectors vs ArrayList
>Date: Thu, 24 May 2001 12:00:59 -0700
>
>That is what was proposed and voted on, so you will be happy whenever
>someone implements it.
>
>john mcnally
>
>Kasper Nielsen wrote:
> >
> > I would prefer if the various functions returned a java.util.List
> > (interface) this way we can return both Thread safe and non Thread safe
> > data.
> > You should be thinking about the interfaces rather than the 
>implementations.
> > But it will break a lot of code no matter what the Vectors is replaced 
>by.
> >
> > - Kasper
> >
> > ----- Original Message -----
> > From: "Colin Chalmers" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, May 24, 2001 6:50 PM
> > Subject: Re: Vectors vs ArrayList
> >
> > > Does this mean that we should/will replace *all* vectors with 
>ArrayLists
> > or
> > > only specific ones? Will this not break some code?
> > >
> > > /colin
> >
> > ---------------------------------------------------------------------
> > 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]
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to