Fields interfering with method resolution for Scala Dynamic trait?

Question

As my first foray into Dynamic Scala land, I thought that I'd try accessing bean properties via applyDynamic.

My first very rough cut is

trait BeanProperties extends Dynamic {
  def applyDynamic(name: String)(args: Any*) = {
    if (args.length == 0)
      PropertyUtils.getProperty(this, name)
    else
      null
  }
}

so that

val bean = new JTextField("text") with BeanProperties
bean.getText should equal("text")
bean.text should equal("text")

so far so good! But when I try

bean.background should equal(bean.getBackground)

the compiler complains, trying instead to give access to the field named background rather than synthesizing a method.

variable background in class Component cannot be accessed in javax.swing.JTextField with BeanPropertiesTest.this.BeanProperties

Is this by design, an oversight, or something that is planned to be fixed?

Quite a bit of lurking interest it seems, but no one has any thoughts - and the Scala mailing lists are curiously silent. — Duncan McGregor, Jun 03 '11 at 13:18

score 2 · Accepted Answer · answered Oct 02 '11 at 21:52

2

FWIW, I proposed a fix for this https://github.com/scala/scala/pull/98

If it is accepted, it will indeed be fixed by the time Dynamic comes out of -Xexperimental.

answered Oct 02 '11 at 21:52

jsalvata

2,155
15
32

score 0 · Answer 2 · answered Jun 14 '11 at 07:15

0

Answer on the Scala-Lang mailing list from Martin Odersky

I think this should be fixed by the time Dynamic comes out of -Xexperimental.

answered Jun 14 '11 at 07:15

Duncan McGregor

17,665
12
64
118

Fields interfering with method resolution for Scala Dynamic trait?

2 Answers2