> The net result is that a PL/I programmer would have to work very hard to program a buffer overflow error, while a C programmer has to work very hard to avoid programming a buffer overflow error.
;-)
I am in favor of -fbounds-safety, -fsanitize=address, etc. for any C/C++ software where you don't want memory errors.
> The net result is that a PL/I programmer would have to work very hard to program a buffer overflow error, while a C programmer has to work very hard to avoid programming a buffer overflow error.
;-)
I am in favor of -fbounds-safety, -fsanitize=address, etc. for any C/C++ software where you don't want memory errors.