[Issue 6468] New - Argo complains about words that are "close" to keywords

[email protected] Thu, 11 Jul 2013 14:03:56 -0700 (PDT)
Newsgroups gmane.comp.lang.uml.argouml.issues
Message-ID <[email protected]>
http://argouml.tigris.org/issues/show_bug.cgi?id=6468
                 Issue #|6468
                 Summary|Argo complains about words that are "close" to keyword
                        |s
               Component|argouml
                 Version|0.34
                Platform|PC
                     URL|
              OS/Version|Linux
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|CodeGeneration and ReverseEngineering
             Assigned to|thn
             Reported by|chelmite






------- Additional comments from [email protected] Thu Jul 11 14:03:56 -0700 2013 -------
I tried importing (already working) Java code that has variables "component" and
"type", neither of which are keywords, according to the Java Language
Specification (Java SE 7 Edition). Furthermore, neither is "close" to a keyword
(the only kind of identifiers that are "reserved" in Java). What does "close to"
mean anyway? I didn't find a description of "close to" in the JLS. There are
java keywords that start with the letters "t" or "c". Does starting with the
same letter constitute "close to"?

These identifiers are valid Java and should not be complained about.

Argo sez:

"component" is a reserved word or very close to one.  The names of model
elements must not conflict with reserved words of programming languages or UML.

Using legal names is needed to generate compilable code. 

To address this, use the "Next>" button, or manually select the highlighted
element and use the Properties tab to give it a different name.

------------------------------------------------------
http://argouml.tigris.org/ds/viewMessage.do?dsForumId=448&dsMessageId=3060278

To unsubscribe from this list, e-mail: [[email protected]].
Please do not reply to this mail. Instead, add your comments in the issue.