S, Stéphane Ducasse piše:
> On Dec 14, 2011, at 5:35 PM, Janko Mivšek wrote:
>> Please please, let someone improve Gofer error messages, which are now
>> totally non-understandable. Check in advance if some package is there
>> and say "No package with that name", or even better, "no package with
>> expected name: Blabla6.xxx" or something.
> can you point which messages are a problem
Say you evaluate this script:
Gofer new
squeaksource: 'Fuel';
package: 'ConfigurationOFuel';
load.
(Smalltalk at: #ConfigurationOfFuel) load.
Did you notice a typo in script? Hardly. Now see what exception look like:
Error: Unable to resolve ConfigurationOFuel
GoferPackageReference(Object)>>error:
GoferPackageReference(GoferReference)>>resolveWith:
[:each | each resolveWith: self] in Gofer>>resolved
Array(SequenceableCollection)>>collect:
Gofer>>resolved
...
My thinking: What is it unable to resolve, what is to be resolved
anyway? But if error will be something like:
"Unable to find or resolve package ConfigurationOFuel, check
the name. See Gofer class comment for more"
It will certainly lead me to check for the typo first and only if
failed, go to class comment and find a wiki page.
>> What it is now is unusable, sorry. To prepare a right script is a big
>> pain. Specially because there are nowhere rules how packages are
>> resolved by a name. It will help if in exception at least a link to the
>> some wiki with rules would be shown.
> why don't you use metacello?
> there 45 pages documentation on it
Gofer is needed for Metacello too and yes, Metacello has similar
problems with not very helpful error messages.
See how Fuel guys improve error reporting in recent Fuel, after having
the same cryptic messages before.
Best regards
Janko
--
Janko Mivšek
Aida/Web
Smalltalk Web Application Server
http://www.aidaweb.si
