> Jonathan M Davis:
> > Also, according to TDPL, either your _entire class_ is synchronized, or
> > none of
> > it is. So, synchronized really belongs on the class, not the function, and I
> > wouldn't expect it to compile if only a portion of your functions are
> > synchronized (though I don't kn
Jonathan M Davis:
> Also, according to TDPL, either your _entire class_ is synchronized, or none
> of
> it is. So, synchronized really belongs on the class, not the function, and I
> wouldn't expect it to compile if only a portion of your functions are
> synchronized (though I don't know how cl
On 2010-09-05 02:18, Jonathan M Davis wrote:
On Saturday 04 September 2010 12:06:23 Era Scarecrow wrote:
I'm currently porting a D1 code base to D2 which has the
following class
hierarchy:
interface Map
{
void clear ();
}
class Hashtable : Map
{
synchronized void clear () {};
}
c
On 2010-09-04 21:06, Era Scarecrow wrote:
I'm currently porting a D1 code base to D2 which has the
following class
hierarchy:
interface Map
{
void clear ();
}
class Hashtable : Map
{
synchronized void clear () {};
}
class HashMap : Map
{
void clear () {};
}
When I compiler
On Saturday 04 September 2010 12:06:23 Era Scarecrow wrote:
> > I'm currently porting a D1 code base to D2 which has the
> > following class
> > hierarchy:
> >
> > interface Map
> > {
> > void clear ();
> > }
> >
> > class Hashtable : Map
> > {
> > synchronized void clear () {};
> > }
> I'm currently porting a D1 code base to D2 which has the
> following class
> hierarchy:
>
> interface Map
> {
> void clear ();
> }
>
> class Hashtable : Map
> {
> synchronized void clear () {};
> }
>
> class HashMap : Map
> {
> void clear () {};
> }
>
> When I compiler the co
