If the fediverse circles the drain, we all need to agree we're meeting up at LinkedIn and seriously fucking their shit up.
Senza categoria
2
Post
2
Autori
0
Visualizzazioni
-
If the fediverse circles the drain, we all need to agree we're meeting up at LinkedIn and seriously fucking their shit up.
-
If the fediverse circles the drain, we all need to agree we're meeting up at LinkedIn and seriously fucking their shit up.
@GrimmReality don't bet against the Fediverse.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@jdlh@mstdn.ca I can't recall any cases of usernames using non-ASCII characters, but I do know of a domain name that does. The instance 國漢象會 is one such example.
-
@narF done!
-
Niente, a quest' ora mi sveglia l'angoscia di turno
Questa volta rubavano i computer aziendali
Vabbè almeno cambiano
-
Tips for C Programming from Nic Barker
If you’re going to be a hacker, learning C is a rite of passage. If you don’t have much experience with C, or if your experience is out of date, you very well may benefit from hearing [Nic Barker] explain tips for C programming.
In his introduction he notes that C, invented in the 70s by Dennis Ritchie, is now more than 50 years old. This old language still appears in lists of the most popular languages, although admittedly not at the top!
He notes that the major versions of C, named for the year they were released, are: C89, C99, C11, and C23. His recommendation is C99 because it has some features he doesn’t want to live without, particularly scoped variables and initializing structs with named members using designated initializers. Also C89 is plagued with non-standard integer types, and this is fixed by stdint.h in C99. Other niceties of C99 include compound literals and // for single-line comments.
He recommends the use of clang arguments -std=c99 to enable C99, -Wall to enable all warnings, and -Werror to treat warnings as errors, then he explains the Unity Build where you simply include all of your module files from your main.c file.
It’s stressed that printf debugging is not the way to go in C and that you definitely want to be using a debugger. To elaborate on this point he explains what a segfault is and how they happen.
He goes on to explain memory corruption and how ASAN (short for Address Sanitisation) can help you find when it happens. Then he covers C’s support for arrays and strings, which is, admittedly, not very much! He shows you that it’s pretty easy to make your own array and string types though, potentially supporting slices as well.
Finally he explains how to use arenas for memory allocation and management for static, function, and task related memory.
-
@gatesvp wholeheartedly agree
-
@GrimmReality don't bet against the Fediverse.
-
I really want Trump to pay attention to Gaza long enough to force all parties to come to a ceasefire deal.
-
@benpate we have a task force in the community group, https://github.com/swicg/geosocial
You should join!
