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