Re: Probably a 3.2.5 fix coming
Robert Hairgrove <[email protected]> Wed, 19 Oct 2022 09:28:46 -0400
| Newsgroups | gmane.text.xml.xerces-c.devel |
|---|---|
| Message-ID | <[email protected]> |
On 10/19/22 08:28, Cantor, Scott wrote: > Debian *should* be using C++-11 but isn't, so I'm going to bottom it out, mostly because of my other projects. > > I've patched the use of nullptr out simply for consistency but there's no apparent need to rush out a fix, so I'll let it sit for the time being. > > -- Scott > It looks like the latest Debian is using GCC 4.8.3? `nullptr` has been available in GCC since 4.6, according to this site, and complete support for C++11 is available in 4.8: https://gcc.gnu.org/projects/cxx-status.html#cxx11 However, it is not the default compile mode until GCC 6.1, so it would have to be enabled with the `-std=c++11` command-line option. Many projects, Qt for example, replaced all pointer 0's with `nullptr` sometime between 5.12 and 5.15, so perhaps it wouldn't be such a bad thing just to leave `nullptr` in there? If there ever is another major release, I think this should be used instead of `0` (or `NULL`?? -- I'm not sure what the current state is without diving into the source code). Cheers, Robert