Limitations

• The opC++ Standard Dialect requires a compiler capable of partial template specialization. All recent, major C++ compilers meet this requirement (Visual C++, GNU G++, Intel C++). opC++ as a tool has no such limitations.
• opC++ is currently not type aware. This means it understands headers syntactically - this will be changed in the future to use stricter type behavior. Full type awareness would not likely be fast or correct enough for production use for a number of reasons. Any type issues missed by opC++ will be caught by the back-end compiler with the correct line numbers.
• The opC++ Standard Dialect does not currently allow nested opclasses. This may be fixed soon.

Known Issues

• opC++ Beta v. 0.9

opC++ Beta v. 0.9

• Member functions in namespaced classes require fully scoped return types. Fix is known.
• Member functions using nested classes must use fully scoped return types. Fix involves substituting values, and some level of type awareness.
• Member function return types must use fully scoped typedefs. Fix involves substituting known values, and some level of type awareness.
• Serialization of containers with archivers will clear their contents before loading, this means heap allocated pointer objects may be lost. In the future there may be an auto-deletion mechanism for handling this.