BlogJava-kooyee ‘s blog-随笔分类-Groovy on Grailshttp://www.blogjava.net/Javawind/category/29611.htmlzh-cnFri, 22 Feb 2008 19:53:59 GMTFri, 22 Feb 2008 19:53:59 GMT60新的声明方式，用def定义新属性http://www.blogjava.net/Javawind/archive/2008/02/23/181543.htmlkooyeekooyeeFri, 22 Feb 2008 16:57:00 GMThttp://www.blogjava.net/Javawind/archive/2008/02/23/181543.htmlhttp://www.blogjava.net/Javawind/comments/181543.htmlhttp://www.blogjava.net/Javawind/archive/2008/02/23/181543.html#Feedback0http://www.blogjava.net/Javawind/comments/commentRss/181543.htmlhttp://www.blogjava.net/Javawind/services/trackbacks/181543.html
旧版本中（Groovy JSR 06 的之前版本）@Property定义一个带有setter和getter的私有属性，而def和java中public一样，定义一个公共的属性。

后来@Property已经从Groovy JSR 06中移除，在Grails 0.2和之后的版本中也不会再需要它 。

现在def用来定义一个带有setter和getter的私有属性，来代替了@Property。



参考：http://docs.codehaus.org/display/GroovyJSR/Property+proposal

symbol  meaning
 private
 protected
 public
 final


code field   getter   setter
def x    
final x    
public x    
protected x    
private x    
public final x    
@Property x    
other permutations?      

Proposed

code field   getter   setter note
def x      
final x     the field doesn't need to be final IMHO (dk) My view is that the field should be final(tug)
public x      
protected x      
private x      
public final x
  a public final field like in Java
@Property x      if it's still supported (MrG) My proposal is to remove it (tug)
other permutations?        what happens with static? (MrG) Static behave exactly the same(tug)


kooyee 2008-02-23 00:57 发表评论
]]>