Re: C23 thoughts and opinions

On Sun, 26 May 2024 13:44:32 +0200
jak <nospam@please.ty> wrote:

Keith Thompson ha scritto:

jak <nospam@please.ty> writes: 

Kaz Kylheku ha scritto: 

On 2024-05-24, jak <nospam@please.ty> wrote: 

Bonita Montero ha scritto: 

Am 23.05.2024 um 21:49 schrieb Thiago Adams: 

On 23/05/2024 16:25, Bonita Montero wrote: 

I ask myself what the point is in further developing a
language like this that can actually no longer be saved. 

do you mean C++?
 

>
No, C. 

>
I think you have a lot of confusion about programming languages.
C and C++ are not comparable languages. 

Except for observations like that we can write useful, production
software that compiles as C or C++, but go on ... 

>
Indeed there are c++ compilers who, if used to compile c code,
could decide to call the c compiler to do the work, but if
something in the code is not strictly c, then the compilation will
be in c++, the size of the executable will increase significantly
and will need of an internal or external runtimer to work. If it
were the same thing you would not get different things. 

 
Oh?  Do you know of a C++ compiler that actually behaves this way?
I've never heard of such a thing.
 
C and C++ are closely related, and C and C++ compilers often share
backends, but the two languages have different grammars.  The gcc
command, for example, can invoke either a C or C++ compiler, but it
knows which language it's compiling based on the source file name or
command line options, before it's even seen the content.
 
There are programs that are valid C and valid C++ but with different
behavior.  How would a compiler that behaves as you describe cope
with that?
 

 
For example g++ makes something similar: if you pass a file .C it
compile the C code but if the file (.C) contains C++ code then
compile C++.
 

No, it does not.
g++ compiles as C++ unless you tell it to compile as C with '-x c'
option.