Hi Frank,
Discussing with DamienC and Stef we agree it's a bug, we will fix it.
2013/6/4 Frank Shearar
> On 4 June 2013 10:19, Sebastian Tleye wrote:
> > Hi Frank, i am currently working improving the implementation of traits
> in
> > Pharo,
>
> Excellent!
>
> > 2013/5/31 Frank Shearar
> >>
On 4 June 2013 10:19, Sebastian Tleye wrote:
> Hi Frank, i am currently working improving the implementation of traits in
> Pharo,
Excellent!
> 2013/5/31 Frank Shearar
>>
>> On 31 May 2013 12:32, Stéphane Ducasse wrote:
>> >
>> > On May 31, 2013, at 1:28 PM, Frank Shearar
>> > wrote:
>> >
>>
Hi Frank, i am currently working improving the implementation of traits in
Pharo,
2013/5/31 Frank Shearar
> On 31 May 2013 12:32, Stéphane Ducasse wrote:
> >
> > On May 31, 2013, at 1:28 PM, Frank Shearar
> wrote:
> >
> >> On 31 May 2013 12:01, Damien Cassou wrote:
> >>> Hi Frank,
> >>>
> >>
On 31 May 2013 12:32, Stéphane Ducasse wrote:
>
> On May 31, 2013, at 1:28 PM, Frank Shearar wrote:
>
>> On 31 May 2013 12:01, Damien Cassou wrote:
>>> Hi Frank,
>>>
>>> On Wed, May 29, 2013 at 11:45 PM, Frank Shearar
>>> wrote:
I have a Trait TGroup that requires #*, #identity and #inver
On May 31, 2013, at 1:28 PM, Frank Shearar wrote:
> On 31 May 2013 12:01, Damien Cassou wrote:
>> Hi Frank,
>>
>> On Wed, May 29, 2013 at 11:45 PM, Frank Shearar
>> wrote:
>>> I have a Trait TGroup that requires #*, #identity and #inverse. I want
>>> to construct a TField by composing TGroup
On 31 May 2013 12:01, Damien Cassou wrote:
> Hi Frank,
>
> On Wed, May 29, 2013 at 11:45 PM, Frank Shearar
> wrote:
>> I have a Trait TGroup that requires #*, #identity and #inverse. I want
>> to construct a TField by composing TGroup with itself. One TGroup will
>> form the operations #*, #one,
Hi Frank,
On Wed, May 29, 2013 at 11:45 PM, Frank Shearar wrote:
> I have a Trait TGroup that requires #*, #identity and #inverse. I want
> to construct a TField by composing TGroup with itself. One TGroup will
> form the operations #*, #one, and #reciprocal while the other will
> form #+, #zero
On May 30, 2013, at 11:03 AM, Frank Shearar wrote:
> Hi Stef,
>
> Indeed you'd normally not double apply a trait. I want to do that here
> for explanatory purposes, to show that a field is the melding of two
> groups.
>
> As it turns out, this double application merely highlights my
> underlyi
Hi Stef,
Indeed you'd normally not double apply a trait. I want to do that here
for explanatory purposes, to show that a field is the melding of two
groups.
As it turns out, this double application merely highlights my
underlying issues. My problems would still be there whenever I wanted
to compo
Hi frank
normally it does not make sense to use two times the same trait. So I do not
really understand
how it could work.
So now when you have two traits
T1
T2
minus lets you erase selectively one message x from T1 if it is also available
in T2
and without having to redefine
I have a Trait TGroup that requires #*, #identity and #inverse. I want
to construct a TField by composing TGroup with itself. One TGroup will
form the operations #*, #one, and #reciprocal while the other will
form #+, #zero and #negated.
I don't want #identity or #inverse, because these apply to o
11 matches
Mail list logo
