Re:A comprehensive guide to 50 years of evolution of strict ...
by everslick on Friday November 26, 2021 @03:50AM
(#29348475)
that exact example is given in the document and presented as 1 of 2 possible solutions. I believe, the critique in the parent comment was unwarranted, but I thought I maybe missed something.
Re:A comprehensive guide to 50 years of evolution of strict ...
by jacquesm on Friday November 26, 2021 @03:57AM
(#29348515)
This is the only proper way of doing that. Having pointers to variables on input that functions modify is ugly and error prone. C gets a lot better the moment you try to make your functions as pure as you can.
Re:A comprehensive guide to 50 years of evolution of strict ...
by jcelerier on Friday November 26, 2021 @04:12AM
(#29348589)
As long as you don't return structs, as the compiler may introduce memcpys here. C doesn't have C++'s RVO, last time I checked many cases that GCC and Clang did optimize in C++ weren't optimized in C.
Re:A comprehensive guide to 50 years of evolution of strict ...
by jacquesm on Friday November 26, 2021 @11:03AM
(#29351350)
That works, at the expense of possibly hiding bugs in plain sight. Macros are a double edged sword in that sense, you can almost but not quite create a DSL on top of C that is a lot more safe but it has its drawbacks, and you need to be very good at mentally modeling macro expansion to read and debug code like that in order to ensure that it does what it seems to be saying that it will do.
But yes, sadly I think it's still generally advisable to avoid returning large structs by value.
Note that this has nothing to do with RVO; as I understand it, RVO is about eliding copy constructors, not actual memory copies, and c has no copy constructors and so gets 'RVO' in all cases.
Re:A comprehensive guide to 50 years of evolution of strict ...
by edwcross on Friday November 26, 2021 @03:53AM
(#29348492)
This seems mostly a guide from a 42 School student towards other 42 School students.
It shows one of the issues of having previous-year students teaching younger students: they don't always have enough experience to know the best way to teach things.
Overall, the title is very misleading, a better one would be "42 School Cheat Sheet", ideally with "by a former 42 School student" appended.
Re:A comprehensive guide to 50 years of evolution of strict ...
by resonious on Friday November 26, 2021 @06:11AM
(#29349172)
I recommend searching up "Handmade Hero" if you're interested in getting into C programming and are okay with videos instead of text (though there are text transcriptions)
I think technically he uses a C++ compiler but he doesn't use C++ features. It's the mindset of thinking about the hardware that helps in my opinion.
Also I'm not sponsored or anything. I just really enjoy the series.
Re:A comprehensive guide to 50 years of evolution of strict ...
by montblanc on Friday November 26, 2021 @10:32AM
(#29351087)
Is this what you mean? https://handmadehero.org/ holy crap there's an enormous amount of videos in there. Thing is it's meant for Windows from what I'm seeing and also isn't really divided into topics (let's say I just wanna learn about pointers or about macros).
Re:A comprehensive guide to 50 years of evolution of strict ...
by ac130kz on Friday November 26, 2021 @01:17AM
(#29347907)
I wouldn't call it "strict C programming", the article doesn't talk about strict safety standards, for example, MISRA C. It doesn't even mention _s functions either. I think a proper title should be "common misconceptions and useful tips".
Re:A comprehensive guide to 50 years of evolution of strict ...
by pjmlp on Friday November 26, 2021 @04:03AM
(#29348549)
Indeed, although it is quite sad that the only solution (a long term one) is to turn computers with C Machines with memory tagging, as WG 14 is silent on how to improve the dire state of it.
Re:A comprehensive guide to 50 years of evolution of strict ...
by bestcoder69 on Friday November 26, 2021 @10:15AM
(#29350922)
“Don’t even try to flirt with girls” is an interesting tip for a C programming guide, but I don’t have enough experience with the language to know if it’s wrong. Disclaimer: Happily married java.* programmer.
Re:A comprehensive guide to 50 years of evolution of strict ...
by spacechild1 on Friday November 26, 2021 @07:50PM
(#29355974)
Here's another gem:
int allocate_memory(void)
{
int *matrix;
if (!(matrix = malloc(sizeof(int) * 9))) // this is short for matrix = malloc(sizeof(int) \* 9; if (matrix == NULL)
return NULL; // the malloc is now protected,
return matrix;
}
Re:A comprehensive guide to 50 years of evolution of strict ...
by samisallinen on Friday November 26, 2021 @08:38AM
(#29350084)
At least in computer games that handle lots of 3d coordinate data, floats instead of doubles were/are used to save memory bandwidth + some exedcution time on at least old x87 fpus. Which is also why old versions of DirectX (8 or 9) on windows used set the FPU for half-precision math when initialized.
I stopped even scanning it when the "solution" for the "common beginner mistake" of array overflow is not sizeof() but
``` { const int len = 5; int a[len] = {1,3,5,7,9}; ```
> if you want to modify a value you either have to use a pointer to the memory address:
For the use cases that are too expensive to use functions, macros can be used instead.
However that is only if C++ cannot be used at all, otherwise don't bother.
that's latest GCC, at -O3
But yes, sadly I think it's still generally advisable to avoid returning large structs by value.
Note that this has nothing to do with RVO; as I understand it, RVO is about eliding copy constructors, not actual memory copies, and c has no copy constructors and so gets 'RVO' in all cases.
Noob mistake
https://godbolt.org/z/PzsashEY4
It shows one of the issues of having previous-year students teaching younger students: they don't always have enough experience to know the best way to teach things.
Overall, the title is very misleading, a better one would be "42 School Cheat Sheet", ideally with "by a former 42 School student" appended.
I think technically he uses a C++ compiler but he doesn't use C++ features. It's the mindset of thinking about the hardware that helps in my opinion.
Also I'm not sponsored or anything. I just really enjoy the series.
Whoever wrote this spent a ton of time putting this together but failed at providing value.
But yeah.