Project

General

Profile

Bug #9613

Name collision between DMO class name and FWD classes.

Added by Eduard Soltan over 1 year ago. Updated over 1 year ago.

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

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
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 Eduard Soltan over 1 year ago

I have the following 4GL program:

for each Agent:
    message "Something".
end.

And the following data dump:

ADD TABLE "Agent" 
  AREA "Schema Area" 
  DUMP-NAME "agent" 

ADD FIELD "f1" OF "Agent" AS character 
  FORMAT "x(8)" 
  INITIAL "" 
  POSITION 2
  MAX-WIDTH 16
  ORDER 10

.
PSC
cpstream=ISO8859-1
.
0000000183

It will throw an error at compile phase because of an ambiguity between the DMO class and a internal FWD class com.goldencode.p2j.util.Agent.

[javac] /gcd/dataset/src/com/goldencode/dataset/Start.java:26: error: reference to Agent is ambiguous
    [javac]    Agent.Buf agent = RecordBuffer.define(Agent.Buf.class, "fwd", "agent", "agent");
    [javac]    ^
    [javac]   both interface com.goldencode.dataset.dmo.fwd.Agent in com.goldencode.dataset.dmo.fwd and class com.goldencode.p2j.util.Agent in com.goldencode.p2j.util match
    [javac] /home/es/gcd/dataset/src/com/goldencode/dataset/Start.java:26: error: reference to Agent is ambiguous
    [javac]    Agent.Buf agent = RecordBuffer.define(Agent.Buf.class, "fwd", "agent", "agent");
    [javac]                                          ^

#3 Updated by Vladimir Tsichevski over 1 year ago

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

Also available in: Atom PDF