[Info-vax] 64-bit (was Re: New CEO of VMS Software)
Dave Froble
davef at tsoft-inc.com
Tue Jan 9 18:33:13 EST 2024
On 1/9/2024 2:43 PM, Stephen Hoffman wrote:
> On 2024-01-06 15:30:00 +0000, John Dallman said:
>
>> First, complete the 64-bit API, after all these years. It's a fairly
>> well-defined task, but I don't know how big it is.
>
> There's no way to do that without breaking source-level compatibility, and
> probably not without also doing a migration to a parallel set of 64-bit APIs.
>
> Basically, the image activator examines the image and decides which
> implementation to activate within; the existing 32- and 64-bit implementation,
> or 64-bit new.
>
> This implementation and this migration would also provide an opportunity to toss
> out the most problematic parts of the existing APIs. *stares at password hash
> APIs* *glances at thicket of C API definitions* *rolls eyes at itemlists* *sighs
> and drags BASIC forward to 64-bit and OO*
>
> Some work in the linker and in the image activator here, and a whole lot of work
> in the various user and kernel APIs, and work in app code ranging from build
> procedures to an app overhaul. And work in the docs too, of course.
>
>
Ok, correct me if I'm wrong.
As far as I know, totally 64 bit apps can be implemented on VMS. So, what's the
problem. The fact that there is also that 32 bit capability hanging around
should not be a detriment, right?
I seriously doubt that any Basic users would take advantage of a conversion to
64 bit addresses. So why bother?
--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
More information about the Info-vax
mailing list