Introducing “State..On” syntax to catch events makes a lot of sense. State will wait until one of the listed events happens before it process that event and continue. Call MyFunction1(..) Call MyFunction2(…) State MyState1(MyFunction2) On Error(…) // On Timeout(…) // End This example will test for Error, Timeout and Continue. Continue is implicit…
Don’t worry if some of the stuff in here does your head in – it’s doing my head in as well. At present Plain is no more than a collection of ideas with a lot of loose ends that we hopefully will manage to bring together. We do a lot of multi-threading in Plain –…
Parallel operations (Parallelism) is most often associated with complex math operations. For Plain this is different because we will need it a lot. Imagine my 12 servo robot – it will not be very smooth unless we can operate the servos simultaneously. Syntax for Parallel (or non-blocking) operation is however a bit hard to create.…
Keywords used so far Assign Assign operation. Bit 1 bit data type. Byte 8 bit data type Call Call to a function. Commit Commit parts of a transaction Connect System Diagram – connect modules. Decode Decode a bit field. Domain Encode a bit field. Else Default group in an if statement Elsif Alternative selection in…
We did earlier show how we could call a function in a different module. The previous example illustrated a 1:1 call between modules. What I want to do now is a 1:20 call – I want to make 1 call that execute a function in 20 different modules returning different results. use System Module ComplexMath…
Plain modules run in parallel and we do sometimes need to synchronise access to data or electronics. This is done by the transaction statement. Transaction will delay execution until it is granted exclusive write access to a variable within the domain. This act as an excellent Multi-threading mechanism because it forces the developer to access…
Creating a System Diagram actually makes a lot of sense in a distributed system where you need to program the system rather than individual devices – and it is at the core of what I want to achieve with Plain. A few topics that need some work: Usage of the Interface keyword needs to be…
A lot of Plain assembly syntax is experimental and will be reviewed as we move forward. I think it is important to get concept ideas out in the open for discussions – we can always optimize keywords and syntax later. In Distributed Systems we need to synchronizing data between multiple modules and this creates a need for a…
I have so far designed 3 Hat’s that I have produced, and a few others in draft versions. Looking at my older picktures I seem to have uploaded 3D models, but not so many Pictures of the actual Boards – probably lost some Pictures on the old blog – I will fix that. This is…
The system I described in part 2 needs to send a message from a module in device #2 to a module in device #5. This tree is basically the physical address of a resource as seen from RPI1 and RPI2. But, as this address might change with wirings we need a more generic way to…