| Re: New Object Method Invocation Syntax Brokenness [message #76081] |
Wed, 18 May 2011 15:02  |
chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
|
Senior Member |
|
|
On May 17, 11:37 am, Paulo Penteado <pp.pente...@gmail.com> wrote:
>
> So I would say that what needs to be fixed now is only to make the
> arrow mean, always, method invocation. It should never be accepted for
> a structure field. The resolution of the ambiguity with the dot got
> right in 8.0.1: a field should take precedence over a method.
Hi all,
This is definitely a bug. As Paulo points out, we already fixed the
problem with the "dot". In IDL 8.0.1 and IDL 8.1 the field always
takes precedence over the method, unless "compile_opt idl2" is in
effect. We did this to preserve backwards compatibility - if you had
code that used parentheses, and there was a field with the same name,
then IDL will access the field.
However, it looks like the fix went too far and also included the
arrow. We'll investigate the bug and let you know what we find.
In the meantime, if you run into this problem, you can add
"compile_opt idl2" to resolve the ambiguity.
Thank you.
Cheers,
Chris
ITTVIS
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
