From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Things that OO programming lacks Date: Sun, 16 Nov 2014 19:14:39 +0000 Organization: A noiseless patient Spider Message-ID: References: <87389olqie.fsf@ixod.org> <10d9w.55626$8w1.22302@fx12.iad> <150er0b62wsh3$.1xabmp81w5kdw.dlg@40tude.net> <1azsoc77wjhmi$.1grmnnlq033tz.dlg@40tude.net> <5yzci4a8snfg.1dfsqjyvneeym$.dlg@40tude.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="a84de0bef967d8cbddafca7d81f7b456"; logging-data="14695"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18yDhbz5vsx/YdF3buXszz8dP3rKCjAzSA=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin) Cancel-Lock: sha1:QZV4niIX3Wp2l+HFR+P3qAPZvnY= sha1:cDEfC+Y/f4+GkgOIZmxFs3e04c8= Xref: news.eternal-september.org comp.lang.ada:23424 Date: 2014-11-16T19:14:39+00:00 List-Id: Niklas Holsti writes: > On 14-11-16 19:54 , Simon Wright wrote: >> "Dmitry A. Kazakov" writes: >> >>> I didn't list event-driven AKA data-driven paradigm in my list of >>> paradigms, since it is so horrific, that nobody should seriously >>> consider it as useful. >> >> The event-driven approach to (real-time) software is the only way to >> build such systems: any other way is bound to lead to confusion and >> disaster. >> >> £0.02 > > "No Sale" even at that price (meaning I disagree). > > But of course this depends on what, precisely, is meant by > "event-driven approach". > > It is true that any system that must react to asynchronous inputs, be > they called "events" or whatever, must in its design be "event-driven" > to some extent. But this does NOT mean that the internal architecture > of the SW should be based on message-passing, or FSAs communicating by > events, or anything like that. Such internal architectures > (unfortunately, often the result of the autocode generators of > single-minded model-based design tools) can be HUGELY complex, > inefficient, and beastly to analyse or understand. In my not-so-humble > opinion. I was only trying to make as evidence-free an assertion as Dmitry's. I don't think that we are going to agree on this point, or even have an actual argument, partly because I'm not in a position to produce any evidence myself.