Changes between Version 17 and Version 18 of Ticket #4138


Ignore:
Timestamp:
2016-12-06T15:24:52Z (9 years ago)
Author:
Adrian Pop
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #4138

    • Property Summary NF core → New FrontEnd

  • Ticket #4138 – Description

    v17 v18  
    1 This ticket is tracking the progress on the core of the new frontend. The current status is:
     1This ticket is tracking the progress on the the new frontend. The current status is:
    22
    33 Instantiation (Per, Adrian) 50%::
    … …  
    4242 Flattening (Per) 25%::
    4343   Expansion of array bindings is currently broken and need to be fixed. Subscripting needs to be improved, and the module in general needs to be expanded to keep up with the phases before it.
     44
     45 Connection Handling (Adrian) 40%::
     46   Handling of connect equations using the DAE and the instance tree.
     47
     48 Unit checking (Arun) 100%::
     49   Ported the backend unit checking to the new frontend. Added tests. Based on the DAE intermediate form.
     50
     51 Operator Overloading (Mahder) ::
     52  The support for operator overloading from the current front-end (or the previous implementation of the new front-end) should be ported to the new front-end.
     53
     54 Constant Evaluation (Per) ::
     55  Constant evaluate structural parameters (minimal) or any other constant/parameter bindings (not by default). Per is working on a new type of DAE component reference that will contain a link to the instantiated component tree on which one can do evaluation of bindings.
     56
     57 Function evaluation (Adrian) ::
     58  Sometimes to evaluate structural parameters one needs to evaluate functions. This will port the function interpretation from the current front-end to the new front-end.
     59
     60 Local balance checking (Mahder) ::
     61   This will check the balance checking for each model so that errors can be detected sooner. We had no such support in the current front-end.
     62
     63 Synchronous Features (BernhardT) ::
     64   The handling of the synchronous features (Clocks, etc) and state machines should be ported from the current front-end to the new front-end.