Resolve potential name clash with _init

[FriedrichGretz]

Describe the todo The current code generation produces two C functions for every Blech activity: one for initialising the program counter and one that does the actual reactions.

The former has the same name extended by "_init" which could potentially clash with another codegenerated activity with the actual name "_init".

Task list

• [x] For this release fix the issue with proper name mangling
• [ ] For the future decide whether this _init function is needed at all. Currently, it is there because the caller does not know the names of the program counters of the callee and more crucially does not know which one is the "main thread" program counter. This is because during compilation pc names are generated globally by simply increasing a counter. Instead we could insist that for every activity we start the counter at 1 and thus "pc_1" is always the main thread's pc. Then the caller takes responsibility of setting "subctx->pc_1=2" before calling the callee. (As it used to be before separate compilation was enabled). No _init function is needed in that case.

[FriedrichGretz]

The naming scheme is now

blc_init_01<module>01_<activity>

This name cannot clash with other activity names any more. Furthmore no other identifier will have a blc_init prefix because if "init" were a name in the program, say a module name, it would be surrounded by "01".

This change does not affect the main program level functions "tick" and "init". Those still follow the scheme

blc_blech_01<module>01_tick blc_blech_01<module>01_init

The "blc_blech" prefix prevents clashes with activity names that may be "tick" or "init". Note also, that in the second case the blech infix helps to distinguish a program initialisation "init" from an activity initialisation "init".

In this state the name mangling is (likely) unnecessary complex but prevents all foreseen clashes. The issue is closed.