[Info-vax] RMS record metadata, was: Re: Re; Spiralog, RMS Journaling (was Re: FREESPADRIFT)
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Mon Jun 20 09:54:32 EDT 2016
On 2016-06-20 13:47:48 +0000, John Reagan said:
> On Monday, June 20, 2016 at 9:07:59 AM UTC-4, Stephen Hoffman wrote:
>
>> The vast majority of OpenVMS works well. But there are areas that
>> need to be rethought and refactored. Some changes — like going to a
>> flat address space and away from the current segmented model, or
>> yanking out RMS and its rather baroque record access processing – will
>> never happen. Some — such as seeing executable code in 64-bit space –
>> seem unlikely, but might be possible.
> You can put code into P2 space today on Itanium. Fully supported.
> Just link with /SEGMENT=CODE=P2. The compilers don't care. The
> generated code is the same.
Interesting. (Wanders off to see what C and BASIC do with that...)
> Personally, I'd like to see that be the default in the future. No
> sense cluttering up your P0 space with code especially if you have data
> structures that are still 32-bit address dependent.
Makes sense. P0, P1 and P2 aren't anywhere near as bad as TKB. But
it's still the same segmented address space mess.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list