stackoverflow being arrogant.
i felt that this was created by the suckless community.
only one thing to say. "compatibility comes at a cost."
A very bad title for the post, by the way.
> Why not just use clang? Because clang is painful to use.
There is. You may accomplish preventing any memory leaks or buffer overflows but there always exist a bug in your code.
Well that's how you make companies angry!
stackoverflow being arrogant.
i felt that this was created by the suckless community.
only one thing to say. "compatibility comes at a cost."
A very bad title for the post, by the way.
> Why not just use clang? Because clang is painful to use.
There is. You may accomplish preventing any memory leaks or buffer overflows but there always exist a bug in your code.
Well that's how you make companies angry!