RE: [groovy-dev] I'll give a Groovy presentation at the Jazoon'08

| Different people run into different problems. That's why I'm 
| asking around here. How about you tell me about the problems 
| you have with Groovy?

Well, then it wouldn't be _your_ experiences, obviously 

Anyway, I don't have any problems with Groovy - honestly.
But I do have a whishlist, i.e. things that I would like to
see although they do not hinder me when programming. 
- mocking ctors in MockFor and StubFor
- easier way of calling the original method (think 'super') when
  overriding a method through the MOP
- joint apidoc generation for Java and Groovy code in my project
- interactive Inspector like in the ULC Admin Console
and more minor enhancements that don't even bother me
enough that I would invest the time to write a JIRA issue for
them or fixing them myself.
Ah - and a warning inside IDEA when a refactoring makes a
reference switch from 'known type' (declared or inferred) to
'unknown type'. I will file a JIRA issue for that one soon.

| How would you generate HTML without the "class" attribute?

If you come from Java and expect 
 class
to make your code fail, you can simply use
 'class'
in the builder call.

| I'm guessing that you're talking about the toString() 
| example. I'm mentioning that because my first intuition was 
| that Groovy would figure out which method to override 
| (because there is just one
| toString()) and basically turn my "def" here into "String" 
| (because Groovy eases so many other Java pains). 
| Unfortunately, Groovy 1.0 didn't and so my toString() was 
| never called and I was puzzled why.

Interesting. Then the lesson learned as I understand this is:
"Groovy can make you think it is reading your mind. Be aware
that this is not (always) the case." 

cheers
Dierk

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email