[Pharo-project] Better Gofer error messages
Hi guys, 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. 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. Best regards Janko -- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
On Dec 14, 2011, at 5:35 PM, Janko Mivšek wrote:
Hi guys,
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
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 Stef
Best regards Janko
-- Janko Mivšek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565
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
open a bug entry and we will fix that :) You could even provide the code and it will be faster
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
Done. S, Stéphane Ducasse piše:
open a bug entry and we will fix that :) You could even provide the code and it will be faster
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
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.
I assume you didn't even bother to check the class comment of Gofer, because if you did you would have found a verbatim copy of the wiki article. Lukas -- Lukas Renggli www.lukas-renggli.ch
also here :) https://gforge.inria.fr/scm/viewvc.php/PharoByExampleTwo-Eng/Gofer/Gofer.pdf... Stef On Dec 14, 2011, at 6:17 PM, Lukas Renggli wrote:
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.
I assume you didn't even bother to check the class comment of Gofer, because if you did you would have found a verbatim copy of the wiki article.
Lukas
-- Lukas Renggli www.lukas-renggli.ch
S, Lukas Renggli piše:
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.
I assume you didn't even bother to check the class comment of Gofer, because if you did you would have found a verbatim copy of the wiki article.
Sure I didn't and hardly anyone will come to this idea when seeing this cryptic error. Of course if error message would lead me to class comment, things would be different. This error is frequent, so error message should be more descriptive, this is my point. Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
participants (3)
-
Janko Mivšek -
Lukas Renggli -
Stéphane Ducasse