Project

General

Profile

Bug #11206

CommonFrame Name Clashes in Converted Java Code

Added by Vladimir Tsichevski 5 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
16417
version_resolved:
reviewer:
production:
No
env_name:
topics:

Related issues

Related to Database - Bug #6767: Possible name clashes in DMO classes Review

History

#1 Updated by Vladimir Tsichevski 5 months ago

Conversion of this simple 4GL code:

DEFINE VARIABLE x AS CHARACTER NO-UNDO.

produces an uncompilable Java interface:

public interface XXXFrame0
   extends CommonFrame
{
   ...
   public character getX();
   ...
}

This results in the following compilation error:

[javac] XXXFrame0.java:11: error: getX() in XXXFrame0 clashes with getX() in CommonFrame
[javac] public character getX();
[javac] ^
[javac] return type character is not compatible with NumberType

The generated getter method getX() clashes with the inherited method from CommonFrame:

public NumberType getX();

This happens when a 4GL variable is named x (or any name that collides with existing CommonFrame methods).

#2 Updated by Vladimir Tsichevski 5 months ago

  • Related to Bug #6767: Possible name clashes in DMO classes added

Also available in: Atom PDF