[Pharo-project] Issue 1659: WACallSuperImplementationRule>>checkClass: on a SmalllintContext ObjectTracer causes walkback
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: PharoCore1.0rc1 [Latest update: #10500] SystemBrowser default = Browser Steps to reproduce: 1.From Browser, right click any class 2.refactor > code critics 3.opens Code Critics: All checks on Smalltalk 4. walkback occurs checking ObjectTracer - no superclass -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
I cannot reproduce that problem. That would be a bug in Seaside anyway (it is a lint rule of Seaside). Lukas 2009/12/22 Stan Shepherd <stan.shepherd414@gmail.com>:
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: PharoCore1.0rc1 [Latest update: #10500]
SystemBrowser default = Â Browser Steps to reproduce: 1.From Browser, right click any class 2.refactor > code critics 3.opens Code Critics: All checks on Smalltalk 4. walkback occurs checking ObjectTracer - no superclass -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
Ahh, I found out that this is in the WebDev image, not in PharoCore. Fixed in the latest Seaside code. 2009/12/22 Lukas Renggli <renggli@gmail.com>:
I cannot reproduce that problem.
That would be a bug in Seaside anyway (it is a lint rule of Seaside).
Lukas
2009/12/22 Stan Shepherd <stan.shepherd414@gmail.com>:
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: PharoCore1.0rc1 [Latest update: #10500]
SystemBrowser default = Â Browser Steps to reproduce: 1.From Browser, right click any class 2.refactor > code critics 3.opens Code Critics: All checks on Smalltalk 4. walkback occurs checking ObjectTracer - no superclass -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
Lukas Renggli wrote:
Ahh, I found out that this is in the WebDev image, not in PharoCore.
Fixed in the latest Seaside code.
2009/12/22 Lukas Renggli <renggli@gmail.com>:
I cannot reproduce that problem.
That would be a bug in Seaside anyway (it is a lint rule of Seaside).
Lukas
2009/12/22 Stan Shepherd <stan.shepherd414@gmail.com>:
VM: unix - i686 - linux-gnu - Pharo0.1 of 16 May 2008 [latest update: #10074] Image: PharoCore1.0rc1 [Latest update: #10500]
SystemBrowser default = Â Browser Steps to reproduce: 1.From Browser, right click any class 2.refactor > code critics 3.opens Code Critics: All checks on Smalltalk 4. walkback occurs checking ObjectTracer - no superclass -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
-- Lukas Renggli http://www.lukas-renggli.ch
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thanks Lukas. Sorry, I should have worked out that it goes on the Seaside issues list. This needs updating on http://code.google.com/p/pharo/issues/detail?id=1659 : still shows wontfix. Better still, does google code support moving an issue between projects? Lukas Renggli wrote:
Ahh, I found out that this is in the WebDev image, not in PharoCore.
When I get a walkback, I right click and 'mail out bug report'. This doesn't differentiate core from dev from webdev versions; I'll remember to be explicit. ...Stan -- View this message in context: http://n2.nabble.com/Issue-1659-WACallSuperImplementationRule-checkClass-on-... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Thanks Lukas. Sorry, I should have worked out that it goes on the Seaside issues list. This needs updating on http://code.google.com/p/pharo/issues/detail?id=1659 : still shows wontfix.
for us it means that this is closed but that this is not due to our effort.
Better still, does google code support moving an issue between projects?
not that I know.
Lukas Renggli wrote:
Ahh, I found out that this is in the WebDev image, not in PharoCore.
When I get a walkback, I right click and 'mail out bug report'. This doesn't differentiate core from dev from webdev versions; I'll remember to be explicit.
Sorry, I should have worked out that it goes on the Seaside issues list. This needs updating on http://code.google.com/p/pharo/issues/detail?id=1659 : still shows wontfix.
No problem.
Better still, does google code support moving an issue between projects?
I don't think so. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
participants (3)
-
Lukas Renggli -
Stan Shepherd -
Stéphane Ducasse