On Thu, Jan 6, 2011 at 3:32 PM, Schwab,Wilhelm K <[email protected]>wrote:
> +1. Someone wanting something that "just runs" can/should do something > like > > (MCPackage named: 'HelpSystem' ifNone:'[ DeafObject current ]) unload > Exactly. Now...I don't know the impact of doing this change. Maybe we screw up monticello hehehe cheer mariano > > > Another approach is to trap and log errors so that a lengthy build process > completes and then clearly shows where it encountered problems. > > Bill > > > ________________________________________ > From: [email protected] [ > [email protected]] On Behalf Of Stéphane Ducasse > [[email protected]] > Sent: Thursday, January 06, 2011 6:11 AM > To: [email protected] > Subject: Re: [Pharo-project] why (MCPackage named: 'NonExistenPackage') > unload. doesnt fail ? > > > Do we want that? I am finding a lot of outdated code that uses code like > that and it doesnt fail, but still doesnt unload the package. > > > > For example, cleanUpForRelease does a > > (MCPackage named: 'HelpSystem') unload. > > > > and that package doesnt exist anymore since it was split.... > > > > so...do we want that silent behaviour ? > > probably not. > Better fix the scripts as early as possible > > > > > cheers > > > > mariano > > > >
