Issue 1701: Mapping of IDL constants to Java (java-rtf) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: The IDL to Java mapping specifies that IDL constants are mapped to public static final fields within a Java interface. Examples are shown that include "public static final" modifiers for these fields. The Java Language Specification (Gosling/Joy/Steele) states in section 9.3 that "Every field declaration in the body of an interface is implicitly public, static, and final. It is permitted, but strongly discouraged as a matter of style, to redundantly specify any or all of these modifiers for such fields." I propose that the text and examples be changed to remove the explicit "public static final" modifiers. Resolution: closed issue Revised Text: Actions taken: July 20, 1998: received issue July 30, 1998: closed issue Discussion: End of Annotations:===== Return-Path: Date: Mon, 20 Jul 1998 09:49:56 +0100 From: Simon Nash Reply-To: nash@hursley.ibm.com Organization: IBM To: java-rtf@omg.org Cc: issues@omg.org Subject: Mapping of IDL constants to Java The IDL to Java mapping specifies that IDL constants are mapped to public static final fields within a Java interface. Examples are shown that include "public static final" modifiers for these fields. The Java Language Specification (Gosling/Joy/Steele) states in section 9.3 that "Every field declaration in the body of an interface is implicitly public, static, and final. It is permitted, but strongly discouraged as a matter of style, to redundantly specify any or all of these modifiers for such fields." I propose that the text and examples be changed to remove the explicit "public static final" modifiers. Simon -- Simon C Nash, IBM Java Technology Centre, Hursley, UK MailPoint 146, x245156 Tel. 01962 815156 or +44-1962-815156 Internet: nash@hursley.ibm.com Notes mail: Simon Nash@ibmgb