Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EDT:Core"
Line 11: | Line 11: | ||
***Remove hadcoded functions in Array (get from mof model) | ***Remove hadcoded functions in Array (get from mof model) | ||
***Represent operations and conversions in bindings | ***Represent operations and conversions in bindings | ||
− | ***Remove the binding hierarchy and replace it with IRs (binding level IRs)...requires change to all tooling that uses bindings | + | ***Remove the binding hierarchy and replace it with IRs (binding level IRs)...requires change to all tooling that uses bindings |
***Remove primitive types | ***Remove primitive types | ||
****Compiler provides mapping of primitive type signature to mof signature | ****Compiler provides mapping of primitive type signature to mof signature | ||
Line 29: | Line 29: | ||
**Replace the InternalRef with the proxy types | **Replace the InternalRef with the proxy types | ||
**Rewrite the annoation binder code to be more logical | **Rewrite the annoation binder code to be more logical | ||
+ | |||
+ | *System Parts | ||
+ | **Provide |
Revision as of 09:40, 12 July 2011
Functional Breakdown of EDT Core
- Compiler
- Validation
- Bring validation framework from RBD to EDT
- Use operators to determine compatibility
- Use operators to resolve overloaded functions
- Allow compilers to register their own validators and binders
- Bindings
- Remove hardcoded types (Dictionary, ArrayDictionary, etc)
- Remove hadcoded functions in Array (get from mof model)
- Represent operations and conversions in bindings
- Remove the binding hierarchy and replace it with IRs (binding level IRs)...requires change to all tooling that uses bindings
- Remove primitive types
- Compiler provides mapping of primitive type signature to mof signature
- Validation
- Parser
- Remove primitive type keywords from lexer
- Investigate ways to represent CHAR(20) in grammer
- Treat this as a function and have the compilers provide a mapping to a AST?
- Can the parser be made to treat this as a special delineated type?
- Investigate ways to represent CHAR(20) in grammer
- Remove primitive type keywords from lexer
- Annotations
- Change stereotype to be partype stereotype
- Must support both definition types:
- Record BasicRecord type Annotation
- Record BasicRecord type StereoType
- Must support both definition types:
- Use the defaultType field to tell egl2Mof that stereotype definitions should be mapped to stereoTypeType
- Replace the InternalRef with the proxy types
- Rewrite the annoation binder code to be more logical
- Change stereotype to be partype stereotype
- System Parts
- Provide