Changes between Version 7 and Version 8 of NewFrontEnd

Timestamp:

2017-01-26T00:31:04Z (8 years ago)

Author:

Adrian Pop

Comment:

--

NewFrontEnd

@@ -36 +36 @@
 == Implementation directions ==
 
+=== Core Features ===
+The core features: Instantiation, Extends, Lookup, Modifiers, Redeclare, Imports
+are handled by Per and some of their details is explained above. If there are
+more things to discuss we can put them here. 
+Support for class extends needs to be implemented. Adrian has some work in progress code to be adapted and pushed in.
+
 === Conditional Components ===
-This needs evaluation of structural parameters to work to evaluate the condition. 
+This needs constant evaluation of structural parameters (see below) to work to evaluate the condition.
 The components can stay in place and they can be filtered out together with the connects they are involved in.
 
@@ -55 +61 @@
 end up in the DAE (we can probably use the component tree directly for this).
 The back-end needs the function tree to partially evaluate functions.
+Special care needs to be taken to properly initialize the array sizes in
+functions (topological sorting on dependencies is needed).
 
 === Records ===
@@ -62 +70 @@
 which should (as function calls) include a link to a unique inst node of the 
 records that is to be called/constructed.
+Special care needs to be taken to properly initialize the array sizes in
+records (topological sorting on dependencies is needed).
 
 === Builtin ===
@@ -83 +93 @@
 * expandable connectors
 * inner/outer in the connection sets
-
 
 === Operator Overloading ===
@@ -109 +118 @@
 of these size expressions.
 
+=== Synchronous Features ===
+The handling of the synchronous features (Clocks, etc) and state machines can be ported 
+and adapted from the current front-end to the new front-end. The specification and the ideas 
+from Modelica conference paper can be used. The inner/outer has a connection to this.
+
+=== General discussion ===
+Handling of iterators needs to be implemented. After some internal discussions the easiest
+way to do this is to extend the current class scope with the needed iterators (as we do also
+for the current front-end). 
+
 == Known issues ==