Issue 3118: Boolean attributes (java2idl-rtf)
Source: Borland Software Corporation (Mr. Vijaykumar Natarajan, nobody)
Nature: Uncategorized Issue
Severity: 
Summary: Thought I would raise this as a formal issue.

The spec is ambiguous about mapping boolean accessors when in the following cases


boolean isFoo ();
void setFoo(boolean x);


and

boolean getBar();
boolean isBar();
void setBar(boolean x);

According to the spec, both of the above get mapped to attributes. But, an attribute has only one getter and one setter.
So, the question is what is isBar represented as on the wire? And how is the distinction made between isBar and getBar?

Two ideas I can think of are
1. Drop isBar from being recognized as a getter for attribute bar.
2. Have isBar be represented on the wire as _get_bar. This has the effect of the two methods collapsing into
one on the receiving context, which is probably OK because they should semantically be equivalent anyway.

Resolution: 
Revised Text: 
Actions taken:
December 15, 1999: received issue
May 16, 2006: closed issue
Discussion: 

End of Annotations:=====
Date: Tue, 14 Dec 1999 14:59:05 -0800
From: Vijaykumar Natarajan <vijayn@inprise.com>
Reply-To: vijayn@inprise.com
Organization: Inprise Corporation
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: issues@omg.org, java2idl-rtf@omg.org
Subject: Boolean attributes
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-UIDL: og[d9%-8e9@&J!!fjGe9

Hi,

Thought I would raise this as a formal issue.

The spec is ambiguous about mapping boolean accessors when in the
following cases


boolean isFoo ();
void setFoo(boolean x);


and

boolean getBar();
boolean isBar();
void setBar(boolean x);

According to the spec, both of the above get mapped to
attributes. But, an attribute has only one getter and one setter.
So, the question is what is isBar represented as on the wire? And how
is the distinction made between isBar and getBar?

Two ideas I can think of are
1. Drop isBar from being recognized as a getter for attribute bar.
2. Have isBar be represented on the wire as _get_bar. This has the
effect of the two methods collapsing into
one on the receiving context, which is probably OK because they should
semantically be equivalent anyway.

Vijay