Alex the explicitRequirement was removed because of the algorithms you
need to check for example to update the icons or do static check each
time you compile a method.
Stef
Le 28/8/16 à 11:17, Alexandre Bergel a écrit :
Hi Petr!
You have found what I think is a bug. Indeed, Nautilus may be
> There is no need for explicit requirement in Pharo because it was too static
Sorry, what do you mean by "too static"? Should I use "subclassresponsibility"
in all cases (class and also traits)?
>
>
> Le 28/8/16 à 03:23, Petr Fischer a écrit :
> > Hello, is Trait methods inheritance supported
Today, after some work, I also noticed, that 2 methods from base trait was
"copied" magicaly to the inherited trait (with same implementation as base
trait) - I don't know why and when + Monticello is confused about trait method
changes again...
Bad thing is, these magic issues are nearly irrepr
Hi Petr!
You have found what I think is a bug. Indeed, Nautilus may be improved to have
the behavior you describe. Having an explicit requirement ("self
explicitRequirement”) should be indicated by Nautilus. I suggest you to open a
bug on https://pharo.fogbugz.com
Regarding the second problem,
There is no need for explicit requirement in Pharo because it was too static
Le 28/8/16 à 03:23, Petr Fischer a écrit :
Hello, is Trait methods inheritance supported in Pharo?
Like this:
TBaseTrait>>myMethod
self subclassresponsibility
TSubTrait
uses: TBaseTrait
...
T
Hello, is Trait methods inheritance supported in Pharo?
Like this:
TBaseTrait>>myMethod
self subclassresponsibility
TSubTrait
uses: TBaseTrait
...
TSubTrait>>myMethod
some real implementation
MyClass
uses: TSubTrait
(MyClasss>>myMethod already implemented
