News for hackers. Stuff that matters.
Re:Defense of Lisp Macros by rightbyte on Thursday July 25, 2024 @04:11PM (#41072844)
Simulink is a really nice way to do some control problems in.

Like, the 'flow' is really clear. Adding a feedback, saturation or integral or whatever is clear to the eye.

Stateflow charts are also a really nice way to do statemachines, which are used alot in automotive.

Simulink is terrible in many ways too, but in some perverted way I like it for the specific usecase.

Re:Defense of Lisp Macros by phkahler on Thursday July 25, 2024 @04:36PM (#41073099)
>> Simulink is a really nice way to do some control problems in.

Agreed. But it needs to stop there. BTW I never understood why the tool needs to know what processor the code is for. I asked them to provide a C99 target so they don't need to define their own data types in generated code. Does that exist yet? Or do they still define their own UINT_16 types depending on the target?

Re:Defense of Lisp Macros by rightbyte on Thursday July 25, 2024 @07:28PM (#41074525)
Dunno and I haven't worked with Simulink since 2019. There is this "type replacement" setting such that you can make Coder spit out "uint16_t" instead, but if I remember correctly, there was bugs such that you still needed to have the manual translation header. Like, some module of Simulink didn't follow the setting. God I don't miss working with Mathworks products.

> Agreed. But it needs to stop there.

Heh. Ye ... about that.