On 4 July 2016 at 05:34, Nicklas Karlsson <[email protected]> wrote: > I think of the thread symbol as a clock signal clocking the functions and one > thread could drive several functions. This thread signal is however not a > data path so it might be better to have a thread attribute for functions.
I spend a good proportion of my working day staring fixedly at real-time code written in ASCET, StateFlow and Simulink. Each has its own way to indicate which thread the code is running in. For example Stateflow just has a little box in the top-level dagram: https://imagebin.ca/v/2mswnj5lT8fu I think I prefer the rather more explicit indication in Simulink: https://imagebin.ca/v/2mswd6w7Bx2l But the main thing is that the thread triggers are not shown as coming _from_ anywhere. They have what might be termed a "global scope" -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
