Another video telling people that va_end() 'is not crucial ... What a BAD example ! ... The man page clearly states (and for good reason) that you must call va_end() for each va_start() you called. Telling people in educational videos that this is not necessary is HORRIBLE style. ZERO POINTS, OCEANO! Sorry! If you (for whatever reason use va_start in the same function more than once you will see your finction failing if you do not call va_end ... also, the implementation might change so that va_end is even needed in such a simple example. This is why it is usually always a good idea, to read manpages rather than just playing arround with things ... especially if you intend to tell other people how it works.
U right, My bad. To be clear for others: On macOS, as well as Linux va_end is generally a no-op, meaning it doesn’t perform any observable action in most cases. This is because the va_list is typically implemented in a way that does not require special cleanup. Anyway, as the comment pointed out, you shall always use va_end( ), for Portability, best practice and to avoid undefined behaviours. In my silly 1_function_program example nothing really changes. Zero point for me😂
Your videos are my "go to" whenever I'm stuck, please never stop making these videos and thank you sooo much!
Ty ♥️, good luck with your studies!
This is super comprehensive.I searched a lot about Variadic functions and this one is a game changer. Thank you :)
you are the best one to teach programming, thanks a lot
Thanks to you 👊🏻
thank you for the great video my friend. much love from Nairobi kenya.
Thx for supporting the channel ♥️
This is truly helpful for my ft_printf. Cheers from Lausanne, Switzerland
please can you do a video for advice about pool and how manage our time in
I talk exactly about that with a fellow ;)
~th-cam.com/video/M9shuJWijSg/w-d-xo.html
much love
Ty very much ♥️! Yeah, I'd love to, but unfortunately english is the wildcard language and given that my school is internation I had to kinda use it
never mind you really do a great job keep explaining more and more lessons in c it's very productive👏💪❤👩💻 @@onaecO
7:59 8:41 8:55 mdr
(il a dit zizi !!! issou !!!)
Thanks it was very useful)))
Friend Thx for the kind words ;))
Keep it up
Where is your mail? 😜
thanks for this
Thank you! ;)
Another video telling people that va_end() 'is not crucial ... What a BAD example ! ... The man page clearly states (and for good reason) that you must call va_end() for each va_start() you called. Telling people in educational videos that this is not necessary is HORRIBLE style. ZERO POINTS, OCEANO! Sorry!
If you (for whatever reason use va_start in the same function more than once you will see your finction failing if you do not call va_end ... also, the implementation might change so that va_end is even needed in such a simple example. This is why it is usually always a good idea, to read manpages rather than just playing arround with things ... especially if you intend to tell other people how it works.
U right, My bad.
To be clear for others: On macOS, as well as Linux va_end is generally a no-op, meaning it doesn’t perform any observable action in most cases. This is because the va_list is typically implemented in a way that does not require special cleanup. Anyway, as the comment pointed out, you shall always use va_end( ), for Portability, best practice and to avoid undefined behaviours. In my silly 1_function_program example nothing really changes.
Zero point for me😂