>>32
Nonsensical complaint. Networking shouldn't be part of the standard library.
Im sorry to use imageboard speak but the level of idiocy in this statement is just overwhelming
Hahahohwow.jpg.
GB2 1970s.
Not a library issue. Arguably not even a C issue, but a compiler and OS issue.
Library issue, the OS should only handle them not check programs activly at runtime for them, and the compiler cant even know should you make a routine which accesses memory dynamicly.
So yes it is deffinetly a library issue.
>>32
I'd love to hear you elaborate, but I have a feeling it's just going to be bullshit.
If the linker generates a warning if try to use puts that is real bullshit for me, why include a usefull function if it is "broken"?
everything could be fixed if you would just append a lenght integer upfront of arrays and functions to access them, but no people use C++ instead because its handling is less shitty and nobody likes segfaults.