Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Terje Mathisen <terje.mathisen@tmsw.no>
Newsgroups: comp.arch
Subject: Re: Why VAX Was the Ultimate CISC and Not RISC
Date: Wed, 12 Mar 2025 17:08:51 +0100
Organization: A noiseless patient Spider
Lines: 61
Message-ID: <vqsbij$2mg61$1@dont-email.me>
References: <vpufbv$4qc5$1@dont-email.me>
 <9371fe9be75cdd606c876f539e1d2d78@www.novabbs.org>
 <vqnps4$1j63b$1@dont-email.me>
 <0da86de26bac1912b190793512255aa4@www.novabbs.org>
 <vqo8b1$1ln7o$1@dont-email.me>
 <5e696219dedf30d0095dfd7671a4c87f@www.novabbs.org>
 <vqpuja$22eta$1@dont-email.me> <m3bfusF9ocaU1@mid.individual.net>
 <vqq72r$22et9$1@dont-email.me> <vqqece$273mt$4@dont-email.me>
 <vqqiov$27vt2$3@dont-email.me>
 <0f5c9c5b5826cc6b25b7b5051415fe79@www.novabbs.org>
 <vqr9dh$2finh$2@dont-email.me> <2FgAP.508645$eNx6.257631@fx14.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Injection-Date: Wed, 12 Mar 2025 17:08:52 +0100 (CET)
Injection-Info: dont-email.me; posting-host="2f25f7f3e05f3605f3ad73292b2c9fa3";
	logging-data="2834625"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/AOEiXgo2yM9Hiz/hL/56Q4WM3/WRgyE793Bwjpphs/g=="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101
 Firefox/128.0 SeaMonkey/2.53.20
Cancel-Lock: sha1:godyW7G2ucrjFUvX1FvuvQQKRvQ=
In-Reply-To: <2FgAP.508645$eNx6.257631@fx14.iad>
Bytes: 3863

Scott Lurndal wrote:
> BGB <cr88192@gmail.com> writes:
>> On 3/11/2025 7:51 PM, MitchAlsup1 wrote:
>>> On Tue, 11 Mar 2025 23:58:11 +0000, BGB wrote:
>>>
>>>> On 3/11/2025 5:44 PM, Lawrence D'Oliveiro wrote:
>>>>> On Tue, 11 Mar 2025 13:39:55 -0700, Stephen Fuld wrote:
>>>>>
>>>>>> On 3/11/2025 12:07 PM, moi wrote:
>>>>>>>
>>>>>>> No, it is logically a copy.
>>>>>>
>>>>>> While that is true, I don't think anyone is talking about a "copy"=
 op
>>>>>> code.=C3=82=C2=A0 :-)=C3=82=C2=A0 I had thought about mentioning i=
n the software part of the
>>>>>> argument that COBOL actually has a "move" verb to accomplish that,=
 i.e.
>>>>>> "Move A to B." even though you are technically right that it is a =
copy.
>>>>>
>>>>> There is a language (C++) which has introduced reference operators =
that
>>>>> distinguish between =C3=A2=E2=82=AC=C5=93move semantics=C3=A2=E2=82=
=AC=C2=9D versus =C3=A2=E2=82=AC=C5=93copy semantics=C3=A2=E2=82=AC=C2=9D=
=2E
>>>>>
>>>>> No, I haven=C3=A2=E2=82=AC=E2=84=A2t got my head around it either.
>>>>
>>>> I still haven't seen any good reason to move to C++.
>>>
>>> C++ is for those situations where you want to write a small amount of=

>>> code and have it compile into a vast string of instructions.
>>>
>>
>> Yeah, one can use iostream and have a trivial "hello world" type progr=
am
>> have build times and binary size like it was something quite substanti=
al...
>=20
> You don't have to use iostream.  vsnprintf/snprintf/printf all work
> fine in C++ code and are far more efficient (and far less verbose).
>=20
> Use a subset of C++ (C with classes) and the resulting code is
> quite compact, but you still get data encapsulation and
> inheritance (with a minor perf hit for virtual functions).


This the "C+" language that I started to use several decades ago! Just=20
getting access to local declarations and inline comments was sufficient=20
back then. Now regular C has of course mostly caught up here, but it=20
doesn't matter since I'm using Rust for anything time-critical.

Terje


--=20
- <Terje.Mathisen at tmsw.no>
"almost all programming can be viewed as an exercise in caching"