Smalltalk › Pharo › Pharo Smalltalk Developers

Do we remove TClass?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

3 messages Options

Stephane Ducasse-3

Do we remove TClass?

Hi Happy core developers

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

Stef

Stephane Ducasse-3

Re: Do we remove TClass?

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
<[hidden email]> wrote:
> Hi Happy core developers
>
> do we remove TClass? Because it is duplicated code, no?
>
> Stef

tesonep@gmail.com

Re: Do we remove TClass?

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 <[hidden email]> 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
<[hidden email]> wrote:
> Hi Happy core developers
>
> do we remove TClass? Because it is duplicated code, no?
>
> Stef

Pablo Tesone.
[hidden email]