[Info-vax] Most popular application programming languages on VMS ?

[Dave Froble]

On 1/10/2019 4:39 PM, John Reagan wrote:
> I was discussing with Rob that the documentation for that DLM feature
> is probably buried in some New Features manual or in some CRTL update
> document.  It might not be written down anywhere (it probably
> should).
>
> The CRTL uses the DLM with the range feature (don't think of them as
> bytes in a file, but just a specialization of a normal named lock) to
> be notified of multiple programs that are using the CRTL's
> implementation of fcntl().
>
> http://pubs.opengroup.org/onlinepubs/9699919799/ and search for
> "fcntl".

I'll take a look, but, I don't see how any resource name, being treated 
solely as a resource name, could implement numeric range (better term 
than byte range) locking.

> One could ask for RMS to provide such a feature as part of its
> interface (it would then have to use the DLM to implement it).  If
> that would happen, the CRTL's implementation of fcntl() could be
> greatly simplified.
>
> And back to the question about "code donations", etc., such things
> get really complicated with licenses, ownership, patent protection,
> etc.  For example, if you send me something with a GPL license, I'll
> delete it.

Understood.

>  If you send me something, with copyright to you, I'll
> delete it.

Even if I grant you full and unfettered use of the code, including the 
right to remove copyright?

> If you send me something with no copyright, I'll delete
> it.

Now, that one I just don't understand.  How about if I state that the 
code is a donation to VSI with no strings attached?  How about if I sell 
you the code for $1 ?  Or one cent?

> I believe VSI's agreement with HPE would prevent it; plus GPL
> code might require us to open source vast amounts of OS code (but
> since we aren't the owner, we can't).

I understand that.  But that was not what I was suggesting.

> The process for submitting code to LLVM requires a very specific
> license in the source files AND signed agreements from both the
> engineer and their employer (if available).  And it has been
> controversial as well.  LLVM is updating their license and it having
> to go back and have ALL updates from the beginning of time revetted
> and relicensed.  If the owner does not agree; cannot be found; no
> longer alive; etc., then the code will have to be removed and
> reimplemented.
>

That's just crazy.  But, so is the US legal system ....

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