KIELER Project


Get me back to the home page!

Page tree

Versions Compared

Old Version 19

changes.mady.by.user Alexander Schulz-Rosengarten

Saved on

compared with

New Version Current

changes.mady.by.user Steven Smyth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Find out what's new in the upcoming V2 version 1.0 release of SCCharts!

Table of Contents

...

  • Added Scheduling Directives
  • Added Probabilistic Transitions
  • Added timed automata support for SCCharts

New Expressions

  • Expression language now supports infix assignment operators
  • Expression language now supports bitwise xor and bitwise not
  • Expression language now supports shift operators
  • Expression language now supports the ternary conditional operator
  • Operator precedences are now correctly mapped to the kexpressions model structure
  • Improved host code expressions support 

...

  • Primes can be used in identifier
  • Hostcode now uses accent grave (`)
  • Function call syntax with angle brackets is considered deprecated. It can still be accessed with the extern keyword
  • Semicolon now exclusively stands for the sequence operator. By default you don't need a semicolon as line/command delimiter.
  • To see a complete overview of the SCCharts syntax, please consult our SCCharts syntax page.

What is new in KIELER SCCharts Version 1.0?

...

  • Added dedication data view for simulation values
  • Added live values inside the model diagram
  • Simulation visualization view that links an SVG image to the program state, using a mapping and javascript commands defined in a kiviz file.

What is new in KIELER SCCharts Version 1.0 for Developers?

Grammar Changes

  • A dash (-) is now available in ExtendedIDs. SCCharts States may now include dashes in their IDs.
  • Single underscore (_) IDs are no longer valid. Underscores prefix generated IDs or are Value keywords.

KExpressions

  • Valued Objects in assignments and emissions are now valued object references. Hence, they reuse the KExpressions concepts.
    • If you @inject KEffectsExtensions, you can use the same syntax as before. Otherwise, assignment.reference is the ValuedObjectReference that points to the referenced ValuedObject. You can use the reference as usual. Keep in mind that it is a containment.

Workflow

  • The compiler framework now uses KiCo 3.0. Please consult the developer documentation of KiCo for further questions.
  • The simulation framework now uses the V3 simulation based on KiCo 3.0. Please consult the developer documentation of the simulation for further questions.
  • Most of the test cases now uses the models repository directly. You can specify the location of you models repository in the models_repository variable in your test launch configuration.   Please consult the developer documentation of the test framework for further questions.