Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EDT:Core"

Line 1: Line 1:
 
Functional Breakdown of EDT Core  
 
Functional Breakdown of EDT Core  
 
*Services
 
**EGL XML language elements
 
**JavaObject language element (XmlRecord, AbstractType, or NativeType)
 
  
 
*Compiler  
 
*Compiler  

Revision as of 13:51, 5 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 primitive types
        • Compiler provides mapping of primitive type signature to mof signature
  • 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?
  • Annotations
    • Change stereotype to be partype stereotype
      • Must support both definition types:
        • Record BasicRecord type Annotation
        • Record BasicRecord type StereoType
    • 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

Back to the top