Re: Ada in command / control systems

[Maciej Sobczak <see.my.homepage@gmail.com>]

> How would I pass a complex input to a block, a matrix, user credentials?

I think it has aggregate signals (or buses), even with multiple levels of nesting. That is, what looks like a single line on the screen can be an aggregate of multiple values, even other aggregates.

> The problem is software decomposition and reuse. Simulink's is an ultra 
> low-level language, lower than assembler, IMO.

Then let's stop talking about Simulink. Since the beginning, I'm stressing that it's not Simulink vs. Ada, it's rather MBD vs. source code. That is, don't argue that MBD does not work just because Simulink does not have your pet feature.

> You mean Simulink has a better diagnostics?

You have complained that it crashed after you have hacked its files by hand. Well, I can imagine that some of its later versions might not crash after such abuse. Or that some other tool would not crash. If your argument against MBD depends on some particular tool version crashing, then it's a poor argument. I have crashed compilers, too.

> In my experience OOA&D is dead and buried. None of our customers 
> mentioned in for more than a decade.

Good to know.

> They can keep on inventing more and more bizarre forms of "non-code" to 
> write, that will not make it work.

Then they will keep inventing. Compilers, libraries and frameworks are now free, which makes them kind of hobby thing. There is no business incentive to come back to source code, so companies will do their best to keep us from writing it.

-- 
Maciej Sobczak * http://www.inspirel.com