[Bug-kawa] [bug #39048] Bad method call resolution?

[Per Bothner]

Update of bug #39048 (project kawa):

                  Status:                    None => In Progress            
             Assigned to:                    None => bothner                

    _______________________________________________________

Follow-up Comment #1:

Well, in general a method getImageDescriptor corresponds to a "property" with
the name image-descriptor.  See:
http://www.gnu.org/software/kawa/Field-operations.html
Thus if you write image-descriptor within the scope of a class that has a
method getImageDescriptor, then that is viewed as accessing the property
image-descriptor.

Now, there are two reasons one could view Kawa as doing the wrong thing for
your program:
(1) There is an exact match for image-descriptor, which should take precedence
over getImageDescriptor.
(2) The image-descriptor is in function-call position, so we should not accept
getImageDescriptor for image-descriptor.

Argument (2) is awkward, because we might have a function-valued field -
though that would be rare, and perhaps should require an exact match.

It looks like either or both fixes would be relatively straight-forward (the
relevant code starts line 664 in Translator.java).  However, I have to ponder
a bit (and experiment a bit) to determine the best fix.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39048>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/