[Info-vax] C99 stuff (Re: The Road to V9.0)

[Dave Froble]

On 6/8/2019 10:48 AM, Robert A. Brooks wrote:
> On 6/7/2019 10:08 PM, Dave Froble wrote:
>> On 6/7/2019 5:22 PM, Robert A. Brooks wrote:
>>> On 6/7/2019 3:48 PM, IanD wrote:
>>>> The hobbyist program is eagerly awaited
>>>>
>>>> [...] I've seen little evidence even the new code VSI has written
>>>> for VMS
>>>> will be open sourced.
>>>
>>> It's not going to happen; give it up.
>>>
>>
>> Just curious Rob, is that a business decision, or determined by prior
>> legal agreements?  I've read before that what VSI writes is their own
>> property.
>
> While what we write is ours, what we write is useless without what
> DEC/CPQ/HP(E)
> has written.  Much of the kernel is unchanged from what we've received
> from HPE.
>
> While the port to X86_64 has required a lot of new stuff (memory
> management, for example, is a big area of change), layered products
> (non-compilers), process management, utilities (COPY, DIRECTORY, PCSI,
> etc...) are largely unchanged.
>
> You could not do anything with just the stuff we've written.
>

I agree, and didn't ask that anything be released.

The original question was about "new code", and that is specifically 
what my question was about.  I'm not interested in seeing it happen.  I 
was wondering if there were any restrictions on what VSI writes, and if 
VSI has a policy of not releasing code they write.  I agree, little 
pieces here and there aren't of much independent value.

-- 
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