Ok, no stress. It's not like I've nothing else to do. Let me know once published :-) Jan On 25/01/13 12:32, Stéphane Ducasse wrote:
No I should publish them but I'm slow. and doing too many things ⦠is it related :)?
Stef On Jan 25, 2013, at 9:24 AM, Jan Vrany wrote:
On 24/01/13 18:05, Stéphane Ducasse wrote:
Thanks!
You're welcome! Are your recent changes included in Pharo 2.0 builds? Because I want to have a look at your changes.
Jan
On Jan 24, 2013, at 7:48 AM, Jan Vrany wrote:
Hi,
we've made all SmallLint code in Smalltalk/X MIT-licensed. Enjoy.
Jan
On 22/01/13 23:59, Stéphane Ducasse wrote:
Well. I've written the tag support, so let's make it simple, MIT. I may export a changeset with that code for you, if you like.
Else I will just go over them and it will help me to understand. I think that this is not difficult.
For rules written by CG I'm not sure. You should check with him. But I think it won't be a problem given that you preserve all the signatures and #documentation and #version_XXX methods (we use them to track changes in the source).
However, what I planned (and run out of time :-) is to make tag a first class object with name (symbol) description etc and have class methods to create them. Then one may define and describe meaning of the tag in an extension method. Also, the selection/rejection logic could dispatch back on the tag instance so you may then create fancy dynamic tags (like #portability that automatically includes everything tagged as #pharo #squeak #stx #va, for instance or whatever.
I might hack it later this week, if you would include it into your version (otherwise I've more important things to do :-)
I imagine well. Let us keep it simple. Simple tags with a little class comments are good enough :)
Cheers
On 22/01/13 19:32, Stéphane Ducasse wrote:
Jan what is the license of your tags and other code?
Stef
On Jan 22, 2013, at 3:45 PM, Jan Vrany wrote:
On 22/01/13 18:22, Stéphane Ducasse wrote:
Hi
I'm running the rule RBSubclassResponsibilityNotDefinedRule that
Checks that all subclassResponsibility methods are defined in all leaf classes.
Now the results display the sender of ^ subclassResponsibility but I have to manually find the problems. I would be better to report the violations. Of course this is not that simple: returning a class and missing method.
But this would be much better. Jan did you do that in your version?
Good point. Yes, since now we do that :-)
Jan
Stef
<smalltalkx-lint.zip>