Re: Using const in function arguments.

2024-07-13 Thread Gregory Nutt
The prototypes of standard interface functions  are specified in the POSIX standard.  It would be a POSIX violation to use whatever prototype you happen to like most.  No one gets to "improve" POSIX. read() is specified here https://pubs.opengroup.org/onlinepubs/9699919799/functions/read.html

Re: Using const in function arguments.

2024-07-13 Thread Nathan Hartman
Replying inline below... On Sat, Jul 13, 2024 at 3:21 PM Petro Karashchenko < petro.karashche...@gmail.com> wrote: > Hi, > > This comes more to the edge of coding language paradigms, personal > preferences and readability. > For enable in Rust everything that you define is "const" and if you want

Re: Using const in function arguments.

2024-07-13 Thread Petro Karashchenko
Hi, This comes more to the edge of coding language paradigms, personal preferences and readability. For enable in Rust everything that you define is "const" and if you want to modify it you should explicitly specify it. On another hand in C everything you define is modifiable unless you specify "c

Re: Using const in function arguments.

2024-07-13 Thread michal . lyszczek
On 2024-07-11 23:36:22, Saurav Pal wrote: > Hi all, > > Suppose I have a pointer that I want to pass through function parameters. > In the function, neither is the pointer reassigned, nor is the thing it > points to modified in any form. > > So, I would assume its function argument signature to b