Re: 80386 C compiler

Liste des GroupesRevenir à cl c  
Sujet : Re: 80386 C compiler
De : mutazilah (at) *nospam* gmail.com (Paul Edwards)
Groupes : comp.lang.c
Date : 25. Nov 2024, 01:15:37
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vi0fje$2euio$1@dont-email.me>
References : 1 2 3 4
User-Agent : Microsoft Outlook Express 6.00.2800.1106
"BGB" <cr88192@gmail.com> wrote in message
news:vi0dtn$2ehti$1@dont-email.me...

There are any number of open source C compilers. But they need to be
good enough (too many support only a subset, which may not be enough for
the OP) and they need to be public domain for the OP's purposes.
>
I am more in the camp of MIT or BSD license should be good enough for
most things.

Yes, there are a lot of people in a lot of camps, and this is
where we end up - no public domain C90 compiler
(cc64 is close, but is generated code, and not 80386).

And so that is what I am trying to achieve now. I've given
up waiting for someone else to do it.

Trying to go full public domain has a few of its own issues:

Claimed issues.

* Not always recognized as valid;

I'm happy to say in the documentation that you can use
CC0 instead if you wish.

* Implicitly lacks "No Warranty" and "No Liability" protections for the
author (say, if someone wanted to file a lawsuit over the code being
buggy, etc).

You can add such a disclaimer to anything - copyright or
public domain.

Have you ever heard of anyone in the world ever being sued
for writing public domain code that had a bug in it?

PDOS is public domain. It shouldn't be difficult to find what
could be described as a bug in it.

I encourage you to find a bug in it, try to sue me, and see
how far you get.

Anyway - this is part of the reason why we are where we are.

As for C compilers, I have a compiler for my own uses, but:
* MIT licensed;

Yes, yet another non-public domain C compiler described.

BFN. Paul.



Date Sujet#  Auteur
24 Nov 24 * 80386 C compiler36Paul Edwards
24 Nov 24 +* Re: 80386 C compiler6fir
24 Nov 24 i+* Re: 80386 C compiler2fir
25 Nov 24 ii`- Re: 80386 C compiler1Paul Edwards
24 Nov 24 i`* Re: 80386 C compiler3Bart
25 Nov 24 i `* Re: 80386 C compiler2BGB
25 Nov 24 i  `- Re: 80386 C compiler1Paul Edwards
24 Nov 24 +* Re: 80386 C compiler24Janis Papanagnou
25 Nov 24 i`* Re: 80386 C compiler23Paul Edwards
25 Nov 24 i `* Re: 80386 C compiler22Kaz Kylheku
25 Nov 24 i  +* Re: 80386 C compiler20Rosario19
26 Nov 24 i  i`* Re: 80386 C compiler19Kaz Kylheku
26 Nov 24 i  i +* Re: 80386 C compiler7Keith Thompson
26 Nov 24 i  i i+* Re: 80386 C compiler5Paul Edwards
27 Nov 24 i  i ii`* Re: 80386 C compiler4Keith Thompson
27 Nov 24 i  i ii `* Re: 80386 C compiler3Paul Edwards
27 Nov 24 i  i ii  `* Re: 80386 C compiler2Keith Thompson
27 Nov 24 i  i ii   `- Re: 80386 C compiler1Paul Edwards
28 Nov 24 i  i i`- Re: 80386 C compiler1Tim Rentsch
27 Nov 24 i  i +* Re: 80386 C compiler9David Brown
27 Nov 24 i  i i`* Re: 80386 C compiler8Kaz Kylheku
27 Nov 24 i  i i +* Re: 80386 C compiler6James Kuyper
27 Nov 24 i  i i i`* Re: 80386 C compiler5Kaz Kylheku
28 Nov 24 i  i i i `* Re: 80386 C compiler4James Kuyper
30 Nov 24 i  i i i  `* Re: 80386 C compiler3Kaz Kylheku
30 Nov 24 i  i i i   +- Re: 80386 C compiler1Tim Rentsch
30 Nov 24 i  i i i   `- Re: 80386 C compiler1James Kuyper
28 Nov 24 i  i i `- Re: 80386 C compiler1David Brown
28 Nov 24 i  i +- Re: 80386 C compiler1Tim Rentsch
30 Nov 24 i  i `- Re: 80386 C compiler1Rosario19
26 Nov 24 i  `- Re: 80386 C compiler1Paul Edwards
25 Nov 24 `* Re: 80386 C compiler5Lynn McGuire
26 Nov 24  `* Re: 80386 C compiler4Keith Thompson
26 Nov 24   `* Re: 80386 C compiler3Lynn McGuire
26 Nov 24    `* Re: 80386 C compiler2Keith Thompson
26 Nov 24     `- Re: 80386 C compiler1BGB

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal