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 X-Received: by 2002:a6b:7d47:: with SMTP id d7-v6mr1712025ioq.18.1533756219023; Wed, 08 Aug 2018 12:23:39 -0700 (PDT) X-Received: by 2002:aca:f495:: with SMTP id s143-v6mr125597oih.7.1533756218862; Wed, 08 Aug 2018 12:23:38 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!nntp.giganews.com!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!85.12.16.70.MISMATCH!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!g24-v6no2163308iti.0!news-out.google.com!g5-v6ni1119iti.0!nntp.google.com!g24-v6no2163306iti.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 8 Aug 2018 12:23:38 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=47.185.195.62; posting-account=zwxLlwoAAAChLBU7oraRzNDnqQYkYbpo NNTP-Posting-Host: 47.185.195.62 References: <810948b7-1370-4c0d-aaf3-ed66b7dfbba5@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <39c171ac-8f96-44e1-a086-7a33ab14bc86@googlegroups.com> Subject: Re: Can Ada print coloured/styled text to the terminal? (ANSI escape sequences?) From: "Dan'l Miller" Injection-Date: Wed, 08 Aug 2018 19:23:39 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 4629 X-Received-Body-CRC: 592141380 Xref: reader02.eternal-september.org comp.lang.ada:54096 Date: 2018-08-08T12:23:38-07:00 List-Id: On Wednesday, August 8, 2018 at 1:28:55 PM UTC-5, Dmitry A. Kazakov wrote: > On 2018-08-08 19:59, Randy Brukardt wrote: > > "Per Sandberg" wrote in message > > news:LewaD.910619$aC7.586128@fx03.fr7... > > ... > >> I think you put the finger on the problem with time, and that is that = time > >> implies change. And to require every newly written software to be > >> compatible with every previous compiler does not work since that would > >> mean freezing time. However to require new compilers to accept old cod= e > >> (sometimes with minor modification due to new keywords for example) is > >> complete different story. > >=20 > > That only makes sense for code that was created to be portable. > >=20 > > That requires that the code was compiled on multiple Ada compilers, les= t it > > depend on incorrect implementations of Ada or vendor-specific > > features/interpretations. By definition, that cannot be the case for Ad= a > > 2012 code, since there is no other such compiler. I was only worrying a= bout > > currently supported Ada compilers: ObjectAda (bit of Ada 2012, full Ada > > 2005), Apex (full Ada 2005), Irvine (full Ada 2005), and Janus/Ada (lit= tle > > bit of everything, not a whole lot of anything :-) >=20 > In this context, what about the move AdaCore made recently with GNAT=20 > Community 2018? They disabled all older Ada compatibility modes 83, 95,= =20 > [2005]. Only Ada 2012 is available now. >=20 > Any conspiracy theorists here? (:-)) Just the usual & customary one, as is their habit: AdaCore gives away only= the single =E2=80=A2most-recent=E2=80=A2 stabilized era of Ada (plus parti= al support for the next era) for free in each release, converting any prior= era of Ada over to paying-customers-only. It is a way to strongly encoura= ge users of Ada to pay support fees to avoid churn by staying with, say, Ad= a2005 for many years without any Ada2012 or Ada2020 changes/AIs to existing= -feature semantics. Don't want to pay at all? Then expect semantic churn as Ada2020 features a= re added and as AI-reported defects cause even the slight adjustment within= Ada83-to-Ada2016-era features post-Ada2012's TC1. As based on their past = behavior, I foresee that AdaCore would likely remove Ada2012 support from s= ome future GPL Community Edition once Ada2020 becomes normative & fully imp= lemented. To be fair to AdaCore, it does cost a nontrivial amount of effort to mainta= in Ada83-end-of-era (i.e., Ada87) semantics in isolation from Ada95-end-of-= era (i.e., Ada2000) semantics in isolation from Ada2005-end-of-era (i.e., A= da2007) semantics in isolation from Ada2012-end-of-era (i.e., Ada2016) sema= ntics in isolation from current-wavefront Ada2020-evolving semantics. Chan= ging this without disturbing that at all always costs time, effort, and mon= ey, which in turn is passed on as a value-add to the paying customer who de= arly values that additional level of loving-touch service.