From Newsgroup: comp.lang.ada
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--8323329-311002248-1713348684=:2629
Content-Type: text/plain; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <
78968ac3-2299-c4ba-854c-50ffe049bd5c@insomnia247.nl>
Dmitry A. Kazakov wrote:
"On 2024-01-05 03:00, Randy Brukardt wrote:
"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message news:un64o3$3krch$1@dont-email.me...
...
[. . .]
Usability always trumps performance.
=20
That's the philosophy of languages like Python, not Ada.
=20
Ah, this is why Python is totally unusable? (:-))
=20
I would tend to argue that it is indeed the case that you get dubious
results when you put usability first. Ada puts
readability/understandability, maintainability, and consistency first=20 (along
with performance). Those attributes tend to provide usability, but not at
the cost of making things less consistent or understandable.
=20
I wrote an article on this topic a year and a half ago that I wanted to publish on Ada-Auth.org. But I got enough pushback about not being=20 "neutral"
that I never did so. (I don't think discussing why we don't do things som=
e
other languages do is negative, but whatever.) I've put this on RR's blog=
=20
at
http://www.rrsoftware.com/html/blog/consequences.html so it isn't lost.
Thanks for posting this."
Dear all,
Thanks indeed.
"[. . .]
3. Removing meaningless repetitions contributes to usability. But X :=3D X =
+ Y=20
is only one instance where Ada required such repetition. [. . .]
[. . .]"
I wrote a function to increment as a workaround but opinionated Anita=20
Enmark did not like it. Engineering and opinions.
" if X in T'Class then
declare
XT : T'Class renames T'Class (X);
T'Class is repeated 3 times."
Sorry: 2 times.
With best regards.
Niocl=C3=A1s P=C3=B3l Caile=C3=A1n de Ghloucester --8323329-311002248-1713348684=:2629--
--- Synchronet 3.20a-Linux NewsLink 1.114