| Summary: | i2jpackage option causes reject of valid module definition | ||
|---|---|---|---|
| Product: | JacORB | Reporter: | Steffen Ries <steffen.ries> |
| Component: | IDL compiler | Assignee: | Gerald Brose <gerald.brose> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jacorb |
| Priority: | P2 | ||
| Version: | 2.0 | ||
| Hardware: | PC | ||
| OS: | All | ||
Fixed by a99073fcf32e4eef6db27a50050f7bef85451031 |
NameTable.checkScopingRules() checks scoping rules in translated package names instead of the original package names. This leads to a bogus reject of valid IDL code, when the option "-i2jpackage" is used. Example: $ cat foo.idl module foo { interface bar { }; }; $ idl -i2jpackage foo:foo.foo foo.idl [jacorb.idl] ERROR : foo.idl, line:1(11): Module name foo.foo already defined module foo [jacorb.idl] ERROR : /tmp/foo.idl, line: 5(1): 1 error(s). [jacorb.idl] ERROR : /tmp/foo.idl, line: 5(1): Parse error : Lexer errors The same problem exists in 1.4.0, 1.4.1 and 2.0