[Pharo-dev] Do we remove TClass?

2018-02-11 Thread Stephane Ducasse
Hi Happy core developers

do we remove TClass? Because it is duplicated code, no?

Stef



Re: [Pharo-dev] Do we remove TClass?

2018-02-11 Thread Stephane Ducasse
Then I do not get it what it this

Trait >> private_subclass: t instanceVariableNames: f
classVariableNames: d poolDictionaries: s package: cat
   "Compatibility purposes"
   ^self error: 'Traits cannot have subclasses'.

How raising an error would make something compatible
To be this is stupid code.

Stef



On Sun, Feb 11, 2018 at 5:51 PM, Stephane Ducasse
 wrote:
> Hi Happy core developers
>
> do we remove TClass? Because it is duplicated code, no?
>
> Stef



Re: [Pharo-dev] Do we remove TClass?

2018-02-12 Thread teso...@gmail.com
Hi Stef,
in the new implementation of Traits I have moved that traits to a
package, they are not used at all in the image but they are used by other
projects. For example, they are used by Ficus.

Cheers,
Pablo

On Sun, Feb 11, 2018 at 6:01 PM, Stephane Ducasse 
wrote:

> Then I do not get it what it this
>
> Trait >> private_subclass: t instanceVariableNames: f
> classVariableNames: d poolDictionaries: s package: cat
>"Compatibility purposes"
>^self error: 'Traits cannot have subclasses'.
>
> How raising an error would make something compatible
> To be this is stupid code.
>
> Stef
>
>
>
> On Sun, Feb 11, 2018 at 5:51 PM, Stephane Ducasse
>  wrote:
> > Hi Happy core developers
> >
> > do we remove TClass? Because it is duplicated code, no?
> >
> > Stef
>
>


-- 
Pablo Tesone.
teso...@gmail.com