4 Sep
2008
4 Sep
'08
9:59 a.m.
Hi guys
Fame is changing so we have to fix Moose without knowing the changes
of Fame.
Adrian why don't use deprecated: because we are clients of FAME and
we cannot break each time you change something.
So what do we do?
- solution 1: fork fame
- solution 2: code freeze
Stef
4 Sep
4 Sep
10:09 a.m.
Hi Stef,
You are right, I will use #deprecated: from now on.
Maybe it could help if I mark all published methods as such, so
people can avoid using internal methods. What do you think? In any
case, the published interface of Fame should now be stable. Yesterday
I backported Fame from Squeak to VW even.
cheers,
AA
On 4 Sep 2008, at 9:59 , stéphane ducasse wrote:
Hi guys
Fame is changing so we have to fix Moose without knowing the
changes of Fame.
Adrian why don't use deprecated: because we are clients of FAME
and we cannot break each time you change something.
So what do we do?
- solution 1: fork fame
- solution 2: code freeze
Stef
10:45 a.m.
Ok at least mark them as deprecated: because we cannot get the
infrastrcuture changing for us now.
On Sep 4, 2008, at 10:09 AM, Adrian Kuhn wrote:
Hi Stef,
You are right, I will use #deprecated: from now on.
Maybe it could help if I mark all published methods as such, so
people can avoid using internal methods. What do you think? In any
case, the published interface of Fame should now be stable.
Yesterday I backported Fame from Squeak to VW even.
cheers,
AA
On 4 Sep 2008, at 9:59 , stéphane ducasse wrote:
Hi guys
Fame is changing so we have to fix Moose without knowing the
changes of Fame.
Adrian why don't use deprecated: because we are clients of FAME
and we cannot break each time you change something.
So what do we do?
- solution 1: fork fame
- solution 2: code freeze
Stef
11:30 a.m.
New subject: Public interface of Fame (for Smalltalk)
Hi there,
The public interface of Fame for Smalltalk is pretty stable new (and
testable). To get the specification of the interface print
FMPublicInterface new
and to test it against the current implementation, run
FMPublicInterface suite run
All public method will remain as they are now. Methods not in the
public interface are to be considered internal and subject to future
changes. Please review your code and try to avoid internal methods.
cheers,
AA
On 4 Sep 2008, at 10:45 , stéphane ducasse wrote:
Ok at least mark them as deprecated: because we cannot
get the
infrastrcuture changing for us now.
On Sep 4, 2008, at 10:09 AM, Adrian Kuhn wrote:
> Hi Stef,
>
> You are right, I will use #deprecated: from now on.
>
> Maybe it could help if I mark all published methods as such, so
> people can avoid using internal methods. What do you think? In any
> case, the published interface of Fame should now be stable.
> Yesterday I backported Fame from Squeak to VW even.
>
>
> cheers,
> AA
>
>
>
> On 4 Sep 2008, at 9:59 , stéphane ducasse wrote:
>
>> Hi guys
>>
>> Fame is changing so we have to fix Moose without knowing the
>> changes of Fame.
>> Adrian why don't use deprecated: because we are clients of FAME
>> and we cannot break each time you change something.
>>
>> So what do we do?
>> - solution 1: fork fame
>> - solution 2: code freeze
>>
>> Stef
>>
>>
>
>
5711
days inactive
5711
days old
3 comments
2 participants
participants (2)
-
Adrian Kuhn -
stéphane ducasse