Comments on: DSLs involving existing classes in Groovy http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/ Software engineering in a computational biology environment Mon, 08 Sep 2008 18:02:23 +0000 http://wordpress.org/?v=2.5.1 By: dsl home http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/#comment-139 dsl home Mon, 09 Jun 2008 22:23:37 +0000 http://tiago.org/cc/?p=9#comment-139 <strong>dsl home...</strong> ) Some individuals or companies have abused the TrackBack feature to insert spam links on some blogs (see sping). This enables authors... dsl home…

) Some individuals or companies have abused the TrackBack feature to insert spam links on some blogs (see sping). This enables authors…

]]> By: tiago http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/#comment-55 tiago Thu, 01 May 2008 20:16:23 +0000 http://tiago.org/cc/?p=9#comment-55 Marc, Until you use a foreign library that also messes with core libraries... If you control all the code, then its OK. But if this design pattern becomes common and you use foreign libraries that do this... Marc,

Until you use a foreign library that also messes with core libraries…
If you control all the code, then its OK. But if this design pattern becomes common and you use foreign libraries that do this…

]]> By: Marc http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/#comment-54 Marc Thu, 01 May 2008 17:48:46 +0000 http://tiago.org/cc/?p=9#comment-54 I don't see what the big deal is with changing the core classes. If you have the requisite unit tests, the risks should be minimal. You can also make a rule on the project that nobody messes with core classes until they discuss it with the team first. I think this is a solution looking for a problem. I don’t see what the big deal is with changing the core classes. If you have the requisite unit tests, the risks should be minimal. You can also make a rule on the project that nobody messes with core classes until they discuss it with the team first.

I think this is a solution looking for a problem.

]]> By: tiago http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/#comment-52 tiago Thu, 01 May 2008 09:37:26 +0000 http://tiago.org/cc/?p=9#comment-52 Robert, I actually agree with both your points: 1. I do think there is a problem with anybody being able to change core classes is very large applications using unknown external code (at least there should be a mechanism to force core classes to behave in a default manner). 2. As I said in the post, I don't think the solution is perfect, it is just an avenue that can be explored. At the end of the day I think the problem comes from the mixing of specification and semantics. But that will be the topic of another post. Robert,

I actually agree with both your points:

1. I do think there is a problem with anybody being able to change core classes is very large applications using unknown external code (at least there should be a mechanism to force core classes to behave in a default manner).

2. As I said in the post, I don’t think the solution is perfect, it is just an avenue that can be explored.

At the end of the day I think the problem comes from the mixing of specification and semantics. But that will be the topic of another post.

]]> By: Robert Fischer http://tiago.org/cc/2008/04/30/dsls-involving-existing-classes-in-groovy/#comment-51 Robert Fischer Wed, 30 Apr 2008 23:28:58 +0000 http://tiago.org/cc/?p=9#comment-51 Why is this radd thing better than hacking Number directly? If someone goes in and hacks Number (say, defaulting to String concatenation), you're still just as likely to be screwed. I don't see what you're gaining, and it seems like it's making it harder to figure out what the code is doing. Why is this radd thing better than hacking Number directly? If someone goes in and hacks Number (say, defaulting to String concatenation), you’re still just as likely to be screwed. I don’t see what you’re gaining, and it seems like it’s making it harder to figure out what the code is doing.

]]>