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 X-Google-Thread: a07f3367d7,dea2d62ab1462538 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news3.google.com!feeder.news-service.com!newsfeed.straub-nv.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Writing an Operating System in Ada Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <8e9bc311-7540-40a1-b19e-49e93648c25c@s31g2000yqs.googlegroups.com> <9oyblld05omh$.1dzhmyoseeb7x$.dlg@40tude.net> <414945fd-8ed5-4f42-a237-0685602332b3@f5g2000yqh.googlegroups.com> <1c1x49re1atv3$.kxickttntzsn$.dlg@40tude.net> <8eb51ea9-fd68-4427-9ae5-c64f789c9e43@g1g2000yqi.googlegroups.com> Date: Tue, 19 Jan 2010 20:43:37 +0100 Message-ID: <1vcyna4seea85$.1sdf5wo46sstm.dlg@40tude.net> NNTP-Posting-Date: 19 Jan 2010 20:43:35 CET NNTP-Posting-Host: 40c0736b.newsspool3.arcor-online.net X-Trace: DXC=N?MZQoDe\7g016@cHD@m;jMcF=Q^Z^V3h4Fo<]lROoRa8kFo`eP>Le[6LHn;2LCVn[ On Tue, 19 Jan 2010 10:58:23 -0800 (PST), Shark8 wrote: >>> But that does remind me, I was thinking it would be good to have >>> PostScript as the display for the OS, unifying the visual display that >>> way it would eliminate the need for printer drivers (assuming they're >>> postscript printers) as well as providing a true WYSIWYG for print- >>> preview (MS's print preview can be a bit... inaccurate), right? >> >> Right, but in an OO system you would barely need PostScript. I doubt >> anybody would like to program in PostScript, so what is left? Poor as a >> data carrier, unusable for humans. Doesn't it remind something? XML? (:-)) > > So, what's wrong with it being used as a data-carrier? Nothing, except that there could be better ones and it is uninteresting for the programmer even to know what is actually used as the carrier. >>>> There shall be no interfaces at all. Ada 95 had everything needed, i.e. >>>> abstract types. Introducing interfaces in Ada 2005 was a huge mistake. >> >>> Why do you say that? >> >> Because there should be a honest MI and no interfaces. > > What do you think of [Delphi-style] properties then? Basically they're > an specification of some [virtual] field of an object [with indicators > of it being readable and/or writable] that may either be renaming some > internal field OR the appropriate getter/setter for a field in the > implementation. I rather like the idea because it doesn't pollute the > object-space with so many [publicly visible] getter/setter methods. This is OK, but unrelated to MI. It about separation of implementation and specification, which was not accomplished in Ada with respect to fields. Operations of accessing members should be a primitive. What is visible as a field should be possible to implement either as a physical field or as getter/setter operations. MI is independent on this. It is about membership in more than one disjoint classes. Interface is poor-man's MI, restricted so some artificially chosen cases, which still do not save from either of non-existent MI problems. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de