[Moose-dev] Re: A word about deprecated

Yes, but wouldn't it be good to have a bug tracking system and anytime someone has time they could take a bug off the stack and fix it, Some people are more involved with some packages than others so it would be good to know this as well. Of course I don't have the overview anymore of what is happening in moose as I havent done much general moose coding just dynamoose and a few other small bits and pieces. So I guess this doesn't give me too much of a say in moose. Orla On Jun 13, 2008, at 3:22 PM, Stéphane Ducasse wrote: > Orla > > this is not the problem. I will fix the error reporting and remove > the > deprecation. > Apparently I could not get the message that error reporting is a > nice > feature of an environment (you know a little > console) but apparently this is not useful. > > Now my point is different. From what I see: everybody is perfectly > happy with moose > as it is, and migrating to Squeak + changing Famix + changing from > Meta to Fame does not seem to be a problem > to anybody so perfect. > >> We need a tool to report errors centrally for each version of >> Moose - >> one place for Squeak Moose and one place for VW Moose. >> I agree that the deprecation of a method without fixing the >> callers >> is >> a problem. >> >> Doru is at the football match today so that explains why you are >> not >> getting immediate response. > > Sure there is no problem I was aware of that :) > > Now still this is a good test because in couple of month they may > be > roumanian football matches > everyday. > >> But the whole of moose should not rely on >> Doru otherwise it will die sooner or later. >> >> We could set up a bugzilla. What do you think? >> >> Cheers >> Orla >> >> >> On Jun 13, 2008, at 3:02 PM, Stéphane Ducasse wrote: >> >>> Yes but deprecating a method but not fixing its callers does not >>> help >>> Now I'm stuck. I do not know how to report errors in moose, >>> there >>> is >>> broken code in Moose on VW >>> and on squeak this is not working either. >>> >>> I think that nobody cares about moose expect doru and we feel >>> it. >>> Sad end for Moose. So I will certainly take over but what a >>> pity. >>> >>> Stef >>> >>> On Jun 13, 2008, at 3:01 PM, Orla Greevy wrote: >>> >>>> I do remember this was discussed once along time ago. Dont we >>>> have >>>> some bugzilla type solution? >>>> >>>> If not we should introduce something here... >>>> >>>> Cheers >>>> Orla >>>> >>>> >>>> >>>> >>>> On Jun 13, 2008, at 2:47 PM, stéphane ducasse wrote: >>>> >>>>> Hi guys >>>>> >>>>> I checked and found that >>>>> >>>>> AbstractImporter>>errorLog: is deprecated.... ok fair >>>>> >>>>> Now there are at least 4 methods that invoke this method and >>>>> are >>>>> not >>>>> deprecated. >>>>> So what do we do? >>>>> >>>>> How do we log error in moose? >>>>> We don't? >>>>> >>>>> Stef >>>>> _______________________________________________ >>>>> Moose-dev mailing list >>>>> Moose-dev(a)iam.unibe.ch >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>>> >>>> _______________________________________________ >>>> Moose-dev mailing list >>>> Moose-dev(a)iam.unibe.ch >>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev