Re: technology discussion → does the world need a "new" C ?

On 10/07/2024 17:40, bart wrote:

On 10/07/2024 15:54, Janis Papanagnou wrote:
 

Values passed (including values of pointers [used for arrays]) are
handled (in the functions) as copies and cannot change the original
entities (values or dereferenced objects) in the calling environment.
>
To make it possible to change entities in the calling environment
in "C" you have to implement the necessary indirection by pointers.

 

Your insistence is amazing.

/I/ am amazed at everyone's insistence that there is nothing remarkable about this, and that it is nothing at all like pass-by-reference.

Nobody has said anything close to "it is nothing at all like pass-by-reference".  Many people have made it clear that using pointers - explicitly, or implicitly via the language's automatic decay of array and function expressions to pointers in certain contexts, can be used to give a similar effect to passing by reference.  Indeed, it is precisely the reason C does not have "pass by reference" - it is not needed, as you can conveniently use pointers and "pass by value".

 So, how do I write F in C so that the caller's data is unchanged?

You use a type that you /can/ pass as an argument in C.  You can't pass arrays to functions, or return them.  A convenient method is to wrap the array in a struct :
typedef struct {
uint8_t data[4];
} vector;
If you want to pass around copies of arrays without a fixed predefined size in C, you need to do it all manually - allocate space for copies, copy them, pass the pointer to the first element and the size of the array.  It is one of the things that C does not do for you and you need to do manually, just like most memory management.

 Sure, true pass-by-reference has some extra properties, but if I wanted to duplicate the behaviour of the above in my language, I have to use pass-by-reference.
 In C you get that behaviour anyway (possibly to the surprise of many), in a language which only has pass-by-value, and without needing explicit pointers.

I really don't think any of this is a surprise to many people who make more than a basic effort to learn the language.  It is not hard to understand, as long as you don't fixate on wrong interpretations of how it all works in C.

 That really is remarkable. And not unsafe at all!
 

C is a language that requires more responsibility by the programmer for things that higher level languages handle automatically.  That's the way the language is.  If you don't understand it, you'll make mistakes.
(To be clear here - people have been explaining the facts, not opinions.   Some people here would surely have liked C to be able to pass arrays into and out of functions like other C objects.)