[Info-vax] OpenVMS development tooling
Bill Gunshannon
bill.gunshannon at gmail.com
Wed Sep 29 13:02:38 EDT 2021
On 9/28/21 7:46 PM, Arne Vajhøj wrote:
> On 9/28/2021 6:48 PM, Lawrence D’Oliveiro wrote:
>> On Wednesday, September 29, 2021 at 1:55:39 AM UTC+13, Arne Vajhøj wrote:
>>> On 9/27/2021 10:24 PM, Lawrence D’Oliveiro wrote:
>>>> But then again, with Open Source, the exact architecture doesn’t
>>>> matter as much. It’s easier to port such code across different
>>>> instruction sets, while the proprietary vendors have a hard time.
>>>
>>> The license means absolutely nothing for the porting effort.
>>
>> Real-world experience shows otherwise.
>
> Simple logic tell it to be the case.
>
> Porting foo.c or bar.pas from one platform to another platform
> does not depend on the license at the top as that are comments that does
> not need to be compiled.
>
>> Consider that Linux and the GNU toolset are available across
>> something like two dozen different major processor architectures --
>> basically
>> about one new architecture for every year Linux has been in existence.
>
> But that is because they are written in C and for the most can just
> be compiled on any platform with a C compiler (and maybe a *nix API).
Not really true. Try compiling and running pretty much anything that
floated around comp.sources.anything on a Prime 50 Series running
Primos. Or even under Primix, their Unix API.
bill
More information about the Info-vax
mailing list