Dear Jeff,
On Mon, Nov 23, 2020 at 3:02 PM Jeff Law wrote:
>
> You use a getter function to retrieve the value of ret.to, which is
> fine. Is there a specific reason why you're not using a setter function
> to save the value?
I did this because I have access to ret.to in the libcpp
(Very very gentle ping, just to make sure it's still on anyone's radar...!)
On Fri, Oct 9, 2020 at 8:39 AM JeanHeyd Meneide wrote:
>
> Hello,
>
> > Typo: comple-time
> >
> > >2020-10-08 JeanHeyd "ThePhD" Meneide
> > >
> > >* gcc/c-family/c-cppbuiltin.c: Add predefined macro
> >
Hello,
> Typo: comple-time
>
> >2020-10-08 JeanHeyd "ThePhD" Meneide
> >
> >* gcc/c-family/c-cppbuiltin.c: Add predefined macro
> >definitions for charsets
>
> I think you should put the macro names in braces after the filename and drop
> the trailing "for charsets".
Can do!
>
Dear Joseph,
On Thu, Oct 8, 2020 at 1:36 PM Joseph Myers wrote:
>
> This documentation doesn't seem sufficient to use the macros. Do they
> expand to (narrow) string literals? To an unquoted sequence of
> characters? I think from the implementation that the answer is strings
> (so, in
Dear GCC,
This patch adds macros to the general preprocessor that allow
users to understand what the execution and wide execution charsets
are, which are used for "bark" and L"meow" literals in C-family
languages.
The goal of this is to enable individuals in capable languages
like C
On Sat, Aug 22, 2020 at 8:14 AM Jonathan Wakely via Gcc-patches
wrote:
> I really wish WG14 would just fix the intmax_t mess so we can make
> them integral types unconditionally.
We're trying, but we're struggling to reach a good consensus. Almost
nobody's fully agreeing on one /particular/
