I'm talking about c++ thread my dude
/dpt/ - Daily Programming Thread
I'm trying to print excel sheets to PDF but using the built-in M$ PDF printer gives me a dialog box. I don't want to open the sheet and print line by line because that's the pajeet way of doing it.
That's what the ABA problem stems from. Name one (1) counter example.
> can't write 5 lines without introducing a memory access bug
Programming in C should be a bannable offense, all Cniles should be sent to re-educational camps.
>> can't write 5 lines without introducing a memory access bug
Where? I test that code.
Holy shit that's the book I'm using in one of my classes.
Oooh. That's what I was missing. I was thinking "Man if only there were some way I could just *place* the "&args" argument", but it never occurred to me to use macros.
Thanks user!
Jow Forumsizen in riverdale on e-hentai
Projecting your own shortcomings onto everyone else isn't healthy, user.
A char can have values outside 0..127, either in the negative or up to 255. In either case, there's an out-of-bounds access of ref. Also when char is 0..31, you're accessing ref[-1]. But there's no need to blame yourself, your code is about as safe as a typical C code, it's basically impossible to write good code in it. You should blame yourself for using C tho.
yes that's literally what it stems for
so how are you expected to avoid it? if the answer was simple it would not be a problem
1) never share data between threads
2) never free data
those are the only ways fulfill your advice