Issue 497: Legal IDL cannot map to C++ (cxx_revision) Source: (, ) Nature: Uncategorized Severity: Summary: Summary: Generated C++ (example) ends up with redefinition errors. This is not addressed in current C++ mapping. Options are to amend IDL or to simply state that such IDL cannot be translated. Resolution: close with no change Revised Text: Actions taken: February 5, 1997: received issue June 13, 2000: closed issue Discussion: Close with no change. It's ugly to have these name clashes in the mapping, but the steps required to fix this aren't pretty either, and the name clash is rarely (never?) a problem in practice. End of Annotations:===== X-Authentication-Warning: foxtail.dstc.edu.au: michi owned process doing -bs Date: Wed, 5 Feb 1997 12:54:04 +1000 (EST) From: Michi Henning To: cxx_revision@omg.org Subject: Legal IDL cannot map to C++ Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The following is legal IDL, but cannot be mapped into C++: interface foo { // ... }; interface foo_var { // ... }; interface foo_ptr { // ... }; Clearly, the generated C++ ends up with lots of redefinition errors. This is not addressed in the current C++ mapping. It is difficult to see a way around this problem. One option is to amend IDL to state that if a specification contains an identifier X, then identifiers X_var and X_ptr cannot be used (there are others, depending on circumstances, such as X_forany). The other option would be to simply state that such IDL cannot be translated. Regardless, the C++ mapping should at least address these issues instead of ignoring them. Michi. -- Michi Henning +61 7 33654310 DSTC Pty Ltd +61 7 33654311 (fax) University of Qld 4072 michi@dstc.edu.au This is issue # 497 Legal IDL cannot map to C++ Generated C++ (example) ends up with redefinition errors. This is not addressed in current C++ mapping. Options are to amend IDL or to simply state that such IDL cannot be translated. -Juergen