+100 :) As it is, the image melts down into a retry hell that I can't break and seems to no chance of succeeding. I probably have made mistakes (Migrate has evolved with *every* release of Dolphin and now Pharo). Change is the nature of software, and tweaking loaders goes along for the ride. But I would want errors highlighted so I can fix them if I own them. As it is, I can't get a 1.3 image to build :( Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Sven Van Caekenberghe [sven@beta9.be] Sent: Tuesday, February 07, 2012 1:16 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Building images On 07 Feb 2012, at 19:05, Schwab,Wilhelm K wrote:
It IS killing the experience, and the error handling is too optimistic for its own good, I think??
Well, I am on the side of signalling all exceptional situations immediately. There is no excuse for silently ignoring the fact that a download did not work. Unless the code can successfully deal with the exceptional situation. Sven