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

[Dave Froble]

On 1/14/2019 1:26 PM, Simon Clubley wrote:
> On 2019-01-14, Dave Froble <davef at tsoft-inc.com> wrote:
>> On 1/13/2019 8:24 PM, Simon Clubley wrote:
>>> On 2019-01-12, Dave Froble <davef at tsoft-inc.com> wrote:
>>>>
>>>> I wonder if John can trust the LLVM stuff he's using?
>>>>
>>>
>>> I would say yes he can.
>>>
>>> The LLVM organisation is a large organisation with established procedures.
>>>
>>> That's way different from someone submitting some code to VSI and
>>> claiming it's under a suitable licence.
>>>
>>> I also have no doubt the VSI lawyers gave the LLVM licence and other
>>> other documents (such as contribution guidelines) a _full_ examination.
>>
>> Have to ask, what causes you to have "no doubt"?
>>
>
> David, the fact you even need to ask that question shows just how
> out of touch you are with such things.
>
>> Have you seen any statements to that effect?
>>
>> Have you asked VSI is that is so?
>>
>
> No I haven't and I have no need to do so as such things in today's
> world are as standard as acquiring building insurance and checking
> the legality of employment contracts (for example).

Ah, I now understand.  You have assumed some things, without ever 
checking facts and such.  Well, I guess I need to inform you of what 
happens when you "ass u me".

:-)

>> Perhaps they did, but, what causes you to believe something for which
>> you perhaps have no facts, statements, and such?
>>
>
> I am so sure because if they didn't, it would be something that would
> be completely at odds with today's world.

Stranger things have happened.  For a current example, consider Donald 
Trump.

> You simply do not include something like LLVM into VMS without making
> sure you are not contaminating the rest of VMS with some LLVM licence
> condition as a result of doing so.

Checking on the license terms in no way has anything to do with the 
possibility of some code in the product that should not be there.  Do 
you know if VSI has run testing of all the LLVM code to insure it does 
not contain any possibly copyrighted material.

> You never, never, include code in your product without making sure
> the licence terms for the new code are compatible with the way you
> control and sell your product.

Once again, what does license terms have to do with any code that made 
it's way into LLVM?

> There is no way VSI would decide to start using LLVM without giving
> the LLVM licence conditions a _very_ close examination and making
> sure it's compatible with how VMS is developed and sold.

Not sure why you removed the following from one of my earlier posts?

"Ok, playing devil's advocate here, just warning ...."


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