I knew I especially wanted the latter, since having a Golem as Tank in your group is simply cool! And after trying it out, I can only say: It rocks! (pun intended). I recently got " Dragon Age: Origins", including promotion codes for 2 additional DLCs: "Blood Dragon Armor" and "The Stone Prisoner".
So basically, it fucks up your error-handling - which you will only notice when things actually go wrong. I noticed when the errno-variable was always 0 in that case. Yes, you as a programmer have to tell the system header-files that you want them that you are planning to use them in a multithreaded environment!īut the best part: If you don't set that flag, you probably won't notice right away.
Seems like on Solaris (at least V2.8 for SPARC), if you want to have certain system-library calls behave correctly in a multithreaded environment, you have to set the compiler(!) flag "_REENTRANT". But what I experienced on Solaris really left me baffled. He has to know to call the right reentrant-variants of syscalls whenever possible.
#Dragon age origins dlc unauthorized service code
I understand that the programmer has to ensure his code is thread-safe. Older API-calls easily cause trouble since they are by design not reentrant - or at least their implementation isn't. I think you can safely say that most code these days should be multithread-aware, even if it doesn't feature threads itself. So here's the first one, from quite a while ago already. After watching fefe and Erdgeist bash stupid APIs on the 26C3, I decided to also write/rant about such topics that I came across in the past.
0 kommentar(er)
