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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no 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!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Top 10 Worst C# Features Date: Sat, 5 Sep 2015 08:31:18 +0200 Organization: cbb software GmbH Message-ID: <1s6uj4vbzan40$.1ghcz3js43me7.dlg@40tude.net> References: Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: VL9PesNteoW7ZJu/aOPHLA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:27705 Date: 2015-09-05T08:31:18+02:00 List-Id: On Fri, 4 Sep 2015 16:34:40 -0500, Randy Brukardt wrote: > Opportunity for what, madness? Event-driven GUI programming is just one step > short of madness as it is, I'd hate to expand that. Such code is necessarily > unstructured spaggetti, because every routine has to be able to handle > anything in essentially any order. There are competing relationships which do not map each other. An issuer-handler relationship is a mess because other relationship, the hierarchy of widget types, is considered more important. Another messy relationship is container-child. We cannot have all three structured, thus two of them are necessarily mess. > Much like OOP itself, I don't see it having much application away from the > GUI (and I'm dubious that it is that good of an organization even for a > GUI). GUI is a poor example for OO actually, because of above. > As such, it doesn't make much sense in a general purpose programming > language. Only OOP makes sense. There is *no* application where procedural decomposition is superior to OO decomposition. Procedural decomposition is untyped per design, because procedures can work with existing types only. Therefore you must have all types *before* you start thinking in terms of procedures. So the only types which can be involved are primitive scalar types or messy ad-hoc low-level records and arrays. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de