15 ms·
I have mixed feelings about this, since it's got a lot of great information for someone getting started with C. I can see why you'd want to avoid scattering di
by sevensor 9y ago
I have mixed feelings about this, since it's got a lot of great information for someone getting started with C. I can see why you'd want to avoid scattering dire warnings all over the place, but it skips blithely past a whole host of hazards, stopping briefly only to mention that synchronization can be a cause of threading bugs. It's leading people down the garden path, and then leaving them at the bottom where there's a hungry tiger.
- jws 9y agoThe threading section has a reasonable warning sign before the tiger… All threads can read and write to all memory within that process. This is extremely dangerous, so avoid threading until you have fairly well mastered C without threads. If you must use threads, even if you are experienced, sticking to a model where threads share as little data as possible and very carefully hand off data from one thread to another and then never touch it again is far safer.
- loeg 9y ago> I can see why you'd want to avoid scattering dire warnings all over the place, but it skips blithely past a whole host of hazards Much like the enlightenment codebase itself, unfortunately. If you want to see some quite bad C code, just check out the source.[0] [0]: https://what.thedailywtf.com/topic/15001/enlightened https://what.thedailywtf.com/topic/15001/enlightened
- sevensor 9y agoWow. Glad I use Qt!