Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=C3=B8j?= Newsgroups: comp.os.vms Subject: Re: New VSI post on Youtube Date: Wed, 14 Aug 2024 16:21:39 -0400 Organization: A noiseless patient Spider Lines: 33 Message-ID: References: <66bcf876$0$717$14726298@news.sunsite.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Wed, 14 Aug 2024 22:21:39 +0200 (CEST) Injection-Info: dont-email.me; posting-host="aa4406ae20bba824a9a3b18a6b5d9922"; logging-data="633192"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18iQHxiDTQLX3H53iuyR69yZvhlthx7LVU=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:EapAKKFxcY9DdE1rBX7aINUcfVU= In-Reply-To: Content-Language: en-US Bytes: 2137 On 8/14/2024 3:49 PM, Robert A. Brooks wrote: > On 8/14/2024 2:57 PM, Arne Vajhøj wrote: >> compile/POINTER_SIZE=32, LINK/SEG=CODE=P0 etc. can all help get stuff >> working. >> >> But it is not the right long term solution. > > For C++, the default pointer size should have remained 32. > It was a mistake to change the default from what it was on Alpha and IA64. Given how much C vs C++ issues we have seen, then I think there is a case for that. But as I understand it the plan was to keep C++ very close to out of the box clang. In hindsight ... > There is a lot of VMS-developed C++ code that expects a pointer size of 32, I believe that. > so in the case I cited, that compilation qualifer will remain forever, > because > the code will not change. Unless the system in question has EOL and replacement planned, then I doubt that. Everything eventually change or die. Arne