Opened 10 years ago

Closed 4 years ago

#3073 closed defect (fixed)

Wild card import in a sub package function fails to build the model

Reported by: Ravi Saripalli <ravi.saripalli@…> Owned by: somebody
Priority: high Milestone: 1.16.0
Component: Frontend Version: trunk
Keywords: Cc:

Description

omc version 1.9.2+dev (r23940)

I observe that when I include a wild card import in a subpackage of a user library
library parser can not find the member functions in that package. I am forced to use fully
qualified names. eg.

package A

function test

import A.B.C.* ; this and

x := dummy() ; ... this combo does not work
x := A.B.C.dummy() ; this alone works

package B

package C

function dummy ...

Sample code to illustrate is attached:

Attachments (3)

Test.zip (1.5 KB ) - added by Ravi Saripalli <ravi.saripalli@…> 10 years ago.
Zipped archive of illustration code
Test.2.zip (1.5 KB ) - added by Ravi Saripalli <ravi.saripalli@…> 10 years ago.
Zipped archive of illustration code
Test.3.zip (1.5 KB ) - added by Ravi Saripalli <ravi.saripalli@…> 10 years ago.
source to illustrate the bug

Download all attachments as: .zip

Change History (5)

by Ravi Saripalli <ravi.saripalli@…>, 10 years ago

Attachment: Test.zip added

Zipped archive of illustration code

by Ravi Saripalli <ravi.saripalli@…>, 10 years ago

Attachment: Test.2.zip added

Zipped archive of illustration code

by Ravi Saripalli <ravi.saripalli@…>, 10 years ago

Attachment: Test.3.zip added

source to illustrate the bug

comment:1 by Ravi Saripalli <ravi.saripalli@…>, 10 years ago

apoligies for duplication of attachement ... the browser was playing up ...

comment:2 by Per Östlund, 4 years ago

Component: *unknown*Frontend
Milestone: Future1.16.0
Resolution: fixed
Status: newclosed

If the import is changed to mylib.A.B.C.* (imports must be fully qualified) it now works correctly with both the old and the new frontend.

Note: See TracTickets for help on using tickets.