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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,229ea0001655d6a2 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Newsgroups: comp.lang.ada Subject: Re: Generic Package References: <1177539306.952515.222940@s33g2000prh.googlegroups.com> <9eejm6rqip.fsf@hod.lan.m-e-leypold.de> <19qllkvm6ut42$.1iqo74vjgmsrv$.dlg@40tude.net> <1177801611.10171.32.camel@localhost.localdomain> <1woad6hn9idy2$.6otnwphc1o0h$.dlg@40tude.net> <1177929029.6111.34.camel@localhost> <1177944533.13970.17.camel@localhost> <2aq08qbvw0ym$.1rquampzo7o53.dlg@40tude.net> <1ieq3io2d6nnq$.13818v3y35gnr.dlg@40tude.net> <1178010142.6695.29.camel@localhost.localdomain> <1178026941.16837.88.camel@localhost.localdomain> <1ozvzzh59ebq8$.yeh9do8s3hig$.dlg@40tude.net> <1178055690.27673.39.camel@localhost.localdomain> <1gptkhkkk93hj.1n23zmm3go7tc$.dlg@40tude.net> <1178106506.17912.33.camel@localhost> <1d7fjjn90n15q.tz3xkhxpuz5x.dlg@40tude.net> From: Markus E Leypold Organization: N/A Date: Wed, 02 May 2007 16:21:45 +0200 Message-ID: User-Agent: Some cool user agent (SCUG) Cancel-Lock: sha1:pf4B5ixRGfkmb7WPYxhInTm/OAk= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii NNTP-Posting-Host: 88.72.252.103 X-Trace: news.arcor-ip.de 1178115214 88.72.252.103 (2 May 2007 16:13:34 +0200) X-Complaints-To: abuse@arcor-ip.de Path: g2news1.google.com!news4.google.com!news.germany.com!storethat.news.telefonica.de!telefonica.de!news-fra1.dfn.de!newsfeed.arcor-ip.de!news.arcor-ip.de!not-for-mail Xref: g2news1.google.com comp.lang.ada:15475 Date: 2007-05-02T16:21:45+02:00 List-Id: "Dmitry A. Kazakov" writes: > On Wed, 02 May 2007 13:48:26 +0200, Georg Bauhaus wrote: > >> On Wed, 2007-05-02 at 12:29 +0200, Dmitry A. Kazakov wrote: >> >>>> Memory is not abstract, addresses aren't abstract, >>> >>> In what sense? >> >> When you write a Set implementation for a PC, you can specifying >> addresses and refer to addresses in a consistent way. > > But I am not required to do so. > > BTW 1, it is a quite common programming pattern to share some predefined > states of the container, usually empty ones, but not only. An > implementation of a container of integers could have a reserved > representation for contiguous ranges of integers. For these it would keep > only From and To. Now, let you have a container holding 1, 2, 3, can you > point me the address of 2 there? You're mixing up sufficient and necessary conditions. But never mind: your argument is so jumbled anyway -- why bother with logic :-(. > Another typical pattern is some f applied to the actually kept values, so > "()" actually is a composition f o "()". So what is in the container? > > BTW 2, it is sort of surprising to have such a discussion in c.l.a., for > Ada was one of the first languages introducing a clear distinction between > interface and implementation. Which you have been ignoring all along. The set implementation might use some natural order on the _representation_ of the items, but need not expose it. What one sees (interface) is a set. The order would only be used internally (but one doesn't need even that). >>> for I in ... loop >>> -- what is I'Address here? >> >> irrelevant without computational model. (I didn't say that the >> mentioned abstract addressable node is good for everything. >> But even so, it should not be too difficult to come up with an >> AS-IF model of how I "work"; otherwise, Ada would have an >> insurmountable teaching problem, besides other exegetic trouble.) > > Huh, argumentation to Turing-completeness is a subject of Godwin's Law... Look, who's speaking ... >>>> The proof mentions that Count_Var is initially zero and that >>>> it is only changed by Add_One. Together with the fact that these >>>> are (1) a local variable and (2) a local procedure >>>> closely tied this should imply that pre: Count_Var = 0. >>> >>> So, the precondition is not constant true, it is Count_Var = 0? Then either >>> >>> 1. N = 1 >>> >>> or >>> >>> 2. The program is incorrect, >> >> The program is correct; the assumption that Count_Var = 0 is >> false and not the precondition of Add_One at each time. My fault >> being sloppy. >> ("Count_Var is initially zero and ... is only changed >> by Add_One".) > > That still does not describe the precondition of. In particular, where it > follows that counts S and not something else? S have to appear there. I have not read GBs specification, but just try to understand mine. There you see explicitely which set you're iterating over. And I did not have to use any "order" to specify iteration over a set. > >> So there is a well defined >> operation going on > > It might be a well-defined operation, but its outcome is not. The outcome of a well defined operation (I take that as being well sepcified) does not have to be deterministic. > >>> No, first = [whatever] order. It is same. >> >> How is "whatever order" defined, exactly, and how can I say whatever >> first book will come given a library? > > Merely by saying/writing "first." That defines a book. > >>> Ordering is determined by sole existence of the >>> librarian who can give you a [first] book and continue to do so. >> >> That is, ordering is an outcome of the librarians operation, >> not of the books. > Come on, all orderings are ordered but some orderings are more ordered than > others? (:-)) _WHAT_ is the difference? More likely: What is the meaning of your sentence? > Let you asked somebody to bring > you books in their "proper" order. Other topic. What does "proper" mean here? > How can you determine if he does not > cheat, or just mistakenly used the issue date rather than the birth day of > the author written in Roman numerals and ordered according to Unicode > positions? So? I probably asked to get all those books -- on after the other. I get them. Wether "he" sorts them according to a predefined order or not -- who cares? Do I _have_ to determine wether he cheats? No: Every actual sequence of delivery suffices the requirement. And that is the point you refuse to see. And by the way: Ignoring what I say doesn't make you right. It makes it rather seem probable that you stop "discussing" the moment you're asked to put your cards upon the table and own up to your claims. Regards -- Markus