Update of bug #64486 (project groff):
Status: Need Info => Invalid
Assigned to: None => gbranden
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #4:
[comment #3 comment #3:]
> I must have sent my answer with an e-mail, and not on the web site.
Okay. For some reason I didn't get a copy.
> This is my copy:
>
> Date: Sat, 29 Jul 2023 15:20:06 +0000
> From: Bjarni Ingi Gislason <...>
> To: "G. Branden Robinson" <...>
> Cc: [email protected]
> Subject: Re: [bug #64486] node.cpp: "if (*p == spec)" said to be ambiguous
> (C++20)
> [...]
>
> I use '-std=gnu++23' (and '-std=gnu2x')
Thanks. We don't support that.
INSTALL.extra:
groff is predominantly written in ISO C++98, so you need a C++ compiler
capable of handling this standardized version of the language. The C++
source files use a suffix of '.cpp'; your C++ compiler must be able to
handle this. A C/C++ preprocessor that conforms to ISO C90 is also
required. If you don't already have a C++ compiler, we suggest GCC 9.4
or later. To override the 'configure' script's choice of C++ compiler,
you can set the CXX environment variable to the name of its executable.
HACKING:
Beyond what is said under "Dependencies" in 'INSTALL.extra',
contributors should note that due to the age of the code base, much of
the C++ dialect employed by groff components, while standard, is older
than C++98--closer to Annotated Reference Manual C++ (Ellis, Stroustrup;
Addison-Wesley, 1990). groff implements its own string class and the
Standard Template Library is little used. A modest effort is underway
to update the code to more idiomatic C++98. Where a C++11 feature
promises to be advantageous, it may be annotated in a code comment.
Closing as invalid; the project is not even attempting to support C++23.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64486>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
