#Low-Level Programming Day 1
1 messages · Page 1 of 1 (latest)
or well
just don't cause UB
here is a hint: -fsanitize=undefined to gcc
it helps catch runtime UB
Great language. My mistake. Outdated gives it a bad wrap. It is a good language that exists for many, many years.
Thanks.
basically enables most extra warnings
which I have found to be helpful
C is perfectly adequate
you can write vulnerabilities in any language
Agree
wants to learn programming
being a based god, chooses c
being even more based, chooses this book
well, you're starting out better than i did,
make sure to pass -std=c89 and -pedantic to your compiler as well
or you might get weird warnings since the code in the book is... well, ansi c and the compiler doesn't know that
to add to those opinions, you should always use -Wpedantic -Wall -Wextra -Werror locally, that part on -std=... makes sense due to the book using dated things, sanitizers offer additional runtime checks, which are not totally bulletproof, but useful, so you may want to run your programs after compiling them with e.g. -fsanitize=address,undefined, those all things together will help you catch a lots of problems
thanks for aggregating the suggestions :)
the code on the screenshot has a problem that should be pointed out by compiler with warnings enabled
at the beginning of the thread
oh lemme scroll up
the very first message
no, that's not it
(I mean if you assumed it is C89 then it would be a problem, the missing return, but then the other problem is also there, but completely different than in later C)
correct
pheww
in C89 you cannot declare in for, in later you leave unused variable
and that will be noticed
i thought there was a \m at first because of crappy windows font rendering
ah
anyways op if you want to do something really fun make a random passphrase generator
load up an english dictionary wordlist
randomly pick one word
rinse and repeat until you have enough words in the passphrase