[Tinycc-devel] Re : Re: Re : Re: Where do I get pthread.h?

[david . koch]

Not trolling, I love C, and even more so assembler.

But let's face it, "C" as a language is spawned into many incarnations.

All barely compatible with each other, unless you stick to C89. If so.

About libraries, pthread is not even present on Windows, unless Cygwin or so.

To progress you have to learn from your flaws and failures.

C23 has become a mixture of various other languages out there to the point it 
becomes abhorrent.

https://en.wikipedia.org/wiki/C23_(C_standard_revision)

Only to stay "relevant" yet TCC won't never be able to reach full conformance.

TCC is a great project, but the real priority is bug fixing for already 
established standards.

That the TCC packaging could be misleading is indeed a problem for newcomers.

Hence I made a TCC "distro" more featured (include files) :

https://github.com/Kochise/tinycc_win32/tree/master/win32

Yet still no "pthread.h" hence this fails :

https://github.com/Kochise/tinycc_win32/blob/master/tests/tests2/106_pthread.c

That's be great to provide a complete self sustaining portable package that 
pass all its own tests.

Anyway, I use TCC to compile an old project before Pioneer existed :

https://github.com/Kochise/GLFrontier-win32/blob/main/src/Makefile-tcc.bat

https://github.com/pioneerspacesim/pioneer -> 
https://wiki.pioneerspacesim.net/wiki/FAQ#What.27s_the_history_of_Pioneer

https://pioneerspacesim.itch.io/pioneer / 
https://pioneerspacesim.net/page/download/

So, see, I still use TCC, but try to work around it's limitations.

So not "trolling" that much.

People should deliver a better experience of their beloved language.

Regards.




----- Mail d'origine -----
De: gz8cx4@0w.se
À: tinycc-devel@nongnu.org
Envoyé: Wed, 07 Feb 2024 18:30:43 +0100 (CET)
Objet: Re: [Tinycc-devel]  Re : Re: Where do I get pthread.h?

Regarding a reply to my message:

On Wed, Feb 07, 2024 at 04:04:30PM +0100, david.koch@libertysurf.fr wrote:
> Indeed, I'd say focus on more up to date and elaborate programming languages.
> C, while nice as a "portable assembler" is still full of quirks and tricks.
> Which show how unstable and unprofessional it is 50 years after its creation.
> Many "extensions" and as you state, "unfortunately" packaged by many vendors.

Let us make some observations.

1. This is a list dedicated to a C compiler. Insulting the language of our
interest, with the knowledge of our (mostly quite well informed) choices,
is not a friendly behavior.

2. Historical packaging practices and their unfortunate pedagogical
consequences are not a property of the language. I am quoted in a very
misleading way.

3. What does it actually mean, an "unprofessional" programming language?
Whose professionalism is meant? An insult against its users? Something else?

An incoherent inflammatory message indicates ... trolling.

Not worth to react to.

Regards,
/tccm

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel