[Info-vax] Old work-arounds v. new <stdint.h> (et al.)

[Stephen Hoffman]

On 2022-06-22 17:20:04 +0000, Simon Clubley said:

> On 2022-06-22, Stephen Hoffman <seaohveh at hoffmanlabs.invalid> wrote:
>> On 2022-06-22 14:34:11 +0000, John Reagan said:
>> 
>>> I'm not a huge fan of adding functionality with ECO kits but that is 
>>> the plan at the moment.
>> 
>> Neither am I, but no new versions on the existing VSI platforms, so 
>> that means any new features or enhancements via ECO or UPDATE kits.
>> 
> 
> Then stick the new functionality in an UPDATE kit if those are the only 
> options.
> 
> Placing it in an ECO kit is wrong and I would have thought that VSI 
> would realise that, based on past history.
> 
> Also, the UPDATE kit release notes should be part of the public VMS 
> documentation so that the information they contain never gets "lost".

All patch notes should be part of the public doc, either as patch 
notes, or incorporated into the documentation. As marketing tools, too.

Determining when features got added is already a manual process within 
the V8.4 series.

I too don't like updates via patch kits. But that's where we are, 
pending any future UPDATE kits, and any (entirely hypothetical) 
maintenance releases for Alpha and Itanium.

But I really don't want to see the LOGINOUT mess, or other feature 
forks, either.

>> Various new capabilities and features were added in a number of the 
>> V8.4 UPDATE kits too, and were (only) documented in the patch notes.
>> 
>> That was the enhancement strategy for ~five years or more, too.  
>> Unfortunately, the (published) HPE documentation set was not updated.
>> 
>> Whether the HP and HPE V8.4 UPDATE patch notes are now reflected in the 
>> VSI doc, or if those late-era changes are now nearly forgotten, I've 
>> not checked.
>> 
> 
> IIRC, VSI choose not to take some of the more recent HPE work at the 
> time VSI was formed.

Which only complicates matters.


-- 
Pure Personal Opinion | HoffmanLabs LLC