Custom Query (202 matches)
Results (61 - 63 of 202)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #145 | fixed | CapeArrayInterface | jasper | jasper |
| Description |
The IDL allows for an array of objects in the form of CapeArrayInterface?. In CAPE-OPEN 1.1 this was used only in passing an array of parameter specifications for a parameter array - CAPE-OPEN 1.2 has abandoned this approach. Support for CapeArrayInterface? was overlooked; the basic data type, wrappers, adapters, code generation and marshaling for this type are not implemented. This remained unnoticed because it is not used in CAPE-OPEN 1.2. It could be argued that in an interface design that supports collections, passing an array of objects is not required under any circumstance. Are we dropping IDL support for this unused data type or are we implementing support for it throughout COBIA? |
|||
| #144 | invalid | Code generator drops namespace from adapter | jasper | jasper |
| Description |
Name space is dropped from adapter incorrectly, causing compilation error of generated code. |
|||
| #143 | fixed | Incorrect C++ parsing by code generator | jasper | jasper |
| Description |
Fixes made for #139 broke class manipulation: spacing, base classes and template classes are no longer properly parsed. This causes the code generator to incidentally fail, or otherwise create incorrect code. |
|||