Issue 1090: Reserved names (java-rtf) Source: (, ) Nature: Severity: Summary: Summary: The list of java keywords provided is an old one. > Should this be updated to the following list? > abstract boolean break > byte byvalue case cast catch char > class const continue default do double > else extends final finally float for > future generic goto if implements import > inner instanceof int interface long native > new null operator outer package private > protected public rest return short static > super switch synchronized this throw throws > transient try var void volatile while Resolution: closed issue Revised Text: Actions taken: March 20, 1998: received issue February 19, 1999: closed issue Discussion: End of Annotations:===== Return-Path: Sender: "George M. Scott" Date: Fri, 20 Mar 1998 14:25:05 -0800 From: "George M. Scott" Organization: Visigenic Software, Inc. To: James Pasley CC: java-rtf@omg.org Subject: Re: Reserved Names References: <013901bd5324$675873a0$e7787dc2@orange.aptest.ie> James Pasley wrote: > Here are some comments on the rules for Reserved Names stated insection 23.1.1 of orbos/98-01-16. Java Keywords > The list of java keywords provided is an old one. > Should this be updated to the following list? > abstract boolean break > byte byvalue case cast catch char > class const continue default do double > else extends final finally float for > future generic goto if implements import > inner instanceof int interface long native > new null operator outer package private > protected public rest return short static > super switch synchronized this throw throws > transient try var void volatile while James, I agree there are currently some holes in the name resolution that need to be clarified. This will probably be done as part of a future RTF which will need to consolidate several changes to the Java language mapping including: OBV, POA, Java/IDL mapping, and changes from other RFPs/RTFs. The POA mapping in particular has added new generated names which will need conflict resolution rules associated with them. Also, OBV and Java/IDL require very strict rules for finding a class name given a repository id, so it is essential that the conflict rules are well-defined and applied consistently. In regards to your Java keyword question. I know of no formal document from JavaSoft which specifies that keyword list. I have seen the list you refer to in several places including some very old beta documentation from JavaSoft, but I have not seen that list published as part of the formal definition of the Java language. The list we use is based on the Java Language Specification as published by JavaSoft. If you can give a reference to the JavaSoft document that defines that keyword list, it would be very helpful. George Return-Path: Date: Fri, 20 Mar 1998 14:59:44 -0800 From: Jeff.Nisewanger@Eng.Sun.COM (Jeff Nisewanger) To: james@aptest.ie, gscott@visigenic.com Subject: Re: Reserved Names Cc: java-rtf@omg.org X-Sun-Charset: US-ASCII > In regards to your Java keyword question. I know of no formal > document from JavaSoft which specifies that keyword list. I have > seen the list you refer to in several places including some very old > beta documentation from JavaSoft, but I have not seen that list > published as part of the formal definition of the Java language. > The > list we use is based on the Java Language Specification as published > by JavaSoft. If you can give a reference to the JavaSoft document > that defines that keyword list, it would be very helpful. I will find and distribute the official Java keyword list to this alias but it may not get here for a couple of weeks due to JavaOne activities taking place next week. Jeff