This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
Hi Andre,
I can only speak for myself, but in this case I think your argument
Programming is about constant learning. So you are arguing, that things should
not improve? So that you don't have to learn something new?
does not hold for adding C++ features to gfortran which have no clear
benefit.
There are cases when adding some C++ stuff it is easy to read and
understand for a C programmer. For example, it is fairly easy to guess
what std::swap means, and optional arguments to functions are a concept
that can be quite powerful. I have done so myself on occasion.
I have chosen not to learn much C++, and use C and Fortran instead. If
people start adding too much C++ stuff to gfortran, then I will no
longer be qualified to review patches and to maintain the relevant code
parts.
Regards
Thomas
- References:
- [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler
- Re: [PATCH, Fortran, pr78672, ctp1, v1] Gfortran test suite failures with a sanitized compiler