Simon Wegendt

Progress Tracker: Event System Improvements

3

This is the progress tracker for upcoming changes to the current event system. Feedback is welcome as comments to this! - [ ] Allow events per signal instance - [...

RFC: Signal instance events

2

Introduction ========= The root elements in platforms are system resources. They offer events, modalities and signals. Users can supply event handlers to these events, can read modalities and read and...

This code generates invalid C: ``` package foo; import platforms.x86; var t = `asdf`; ```

**Current behavior:** compiling anything with `HonoMqtt` doesn't work, since keepAliveInterval is not defined. **Expected behavior:** works as before **Other information:** broken by #353

RFC: Default values

1

## Introduction High level language support types that are more defined than numbers, structures and pointers. The most ubiquitous one are Objects. These are structures that carry more semantics and...

Say a function returns just another function: ``` fn foo() { return bar(); } fn bar() { return 4; } ``` Currently this translates to the very verbose C code:...

- [ ] noCompileErrors -> on Bosch server since we need SDK - [ ] Hardware in the loop

You can't reference signal instances in singletons

1

Given a singleton (not named-singleton) SystemResource, any instances configured in it can not be referenced.

Platform generators should be able to generate additional files

1

``` platform.generateAdditionalFiles(IFileSystemAccess2 fsa) : void { } ```

**Current behavior:** Reinitializing strings does not work. **Expected behavior:** Reassigning a variable with `new string(100)` should empty the string. **Related code:** ``` every 100 milliseconds { var s = new...