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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.98.101.199 with SMTP id z190mr411176pfb.48.1503722481738; Fri, 25 Aug 2017 21:41:21 -0700 (PDT) X-Received: by 10.36.121.216 with SMTP id z207mr28864itc.4.1503722481594; Fri, 25 Aug 2017 21:41:21 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!2.eu.feeder.erje.net!feeder.erje.net!2.us.feeder.erje.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!y192no411521itb.0!news-out.google.com!c139ni1245itb.0!nntp.google.com!b76no414237itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 25 Aug 2017 21:41:21 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2601:191:8303:2100:5985:2c17:9409:aa9c; posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3 NNTP-Posting-Host: 2601:191:8303:2100:5985:2c17:9409:aa9c References: <79e06550-67d7-45b3-88f8-b7b3980ecb20@googlegroups.com> <9d4bc8aa-cc44-4c30-8385-af0d29d49b36@googlegroups.com> <1395655516.524005222.638450.laguest-archeia.com@nntp.aioe.org> <4527d955-a6fe-4782-beea-e59c3bb69f21@googlegroups.com> <22c5d2f4-6b96-4474-936c-024fdbed6ac7@googlegroups.com> <3f04ecdc-2672-4051-948f-37ce5446dbac@googlegroups.com> <0950da12-a618-441a-95bb-9ad4c08ce6d9@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <972e5656-9c05-4f83-bdb3-368e65beeabe@googlegroups.com> Subject: Re: Community Input for the Maintenance and Revision of the Ada Programming Language From: Robert Eachus Injection-Date: Sat, 26 Aug 2017 04:41:21 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: news.eternal-september.org comp.lang.ada:47809 Date: 2017-08-25T21:41:21-07:00 List-Id: On Tuesday, August 22, 2017 at 3:34:56 AM UTC-4, Dmitry A. Kazakov wrote:= =20 > > What you want is a tagged type URL. >=20 > Typed with all types necessary. E.g. we need an operations to iterate=20 > directory nodes etc. >=20 > > The base type could have conversions to/from string, with child types > > like local_path, etc., >=20 > I don't directly see how the above types should be rooted in the same=20 > parent. File version has nothing to do with MIME type. You are missing the concept. A URL is well defined today. But say that as= quantum computers become more common, there is a form of locator which use= s set notation: "I want photographs taken September 17, 2012, near these (= Lat/Long) coordinates." URLs are extensible, and there is no reason why yo= u shouldn't have one form for local files, and another for internet resourc= es. The function which converts a text string to a URL can call itself recursiv= ely, or more likely have typed calls to say the part of the function which = processes file names. Hmmm. Another example is that long URL from HTML get accesses. You might = want to have an extension to decode your custom get queries.