This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/78822] [cleanup] replace static char buffers by std:string


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78822

--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to janus from comment #8)
> In general, doesn't this whole memory issue severely limit the usefulness of
> C++ as an implementation language for GCC? It seems to imply that we cannot
> use *any* STL containers? Or do I misunderstand something here?

C++ can be useful even without the STL containers.  Though I'm certainly not
one of the proponents of conversion to C++.

> Again, in the go FE, I see not only extensive usage of std::string, but also
> std::vector etc. I'd like to know why that is ok in the go FE, but not in
> gfortran?

E.g. for std::vector we have an alternative, vec.h, so it is better not to use
std::vector, but vec, for consistency.  About the allocation, I don't know if
somebody hasn't done anything about it, best discuss this on the mailing list
rather than in the PR where others can more easily see it and comment on it.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]