Re: standard error messages in a std::string or in a const char *

From	Manfred <noname@add.invalid>
Newsgroups	comp.lang.c++
Subject	Re: standard error messages in a std::string or in a const char *
Date	2019-09-12 15:44 +0200
Organization	Aioe.org NNTP Server
Message-ID	<qldi3p$13ds$1@gioia.aioe.org> (permalink)
References	(7 earlier) <qlc17j$vp1$1@dont-email.me> <ln1rwmcr17.fsf@kst-u.example.com> <qlc36q$83e$1@dont-email.me> <qld2nl$k2l$1@dont-email.me> <qldab0$u4e$1@dont-email.me>

Show all headers | View raw

On 9/12/2019 1:31 PM, James Kuyper wrote:
> On 9/12/19 5:21 AM, David Brown wrote:
>> On 12/09/2019 02:23, James Kuyper wrote:
>>> On 9/11/19 8:11 PM, Keith Thompson wrote:
>>> ...
>>>> Also, the <*.h> C headers are deprecated as of C++17.
>>>
>>> I hadn't noticed that.
>>>
>>
>> It is not going to make any practical difference, as any real-world C++
>> implementation also supports C, and has the C headers. ...
> 
> If they're deprecated now, it's a warning that they may be removed in
> the future. If they are removed someday, that will give implementations
> permission to no longer provide them, and sooner or later an
> implementation will be created that doesn't. That date might be a long
> time coming, but when it does, it will mark a major step in the
> separation of C++ from C.
> 
>> ...  I guess the aim
>> is to move C++ programmers to use the std:: namespace for standard C
>> functions as much as possible, reducing the global namespace usage.
>>
>> I don't know how that works for macros defined in C standard headers -
>> they can't go into a namespace.
> 
> How it works is that they don't go in a namespace.
> 

Which is not really working, IMVVHO - I mean they compile and do the 
job, but you end up with a mixture of std:: and non-std-qualified names 
which I find ungood at best.
How bad it is varies from one implementation to one other, though.

Back to comp.lang.c++ | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-11 00:35 +0200
  Re: standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-11 00:37 +0200
    Re: standard error messages in a std::string or in a const char * Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-09-11 08:28 +0000
      Re: standard error messages in a std::string or in a const char * Juha Nieminen <nospam@thanks.invalid> - 2019-09-11 08:58 +0000
        Re: standard error messages in a std::string or in a const char * Bonita Montero <Bonita.Montero@gmail.com> - 2019-09-11 11:09 +0200
          Re: standard error messages in a std::string or in a const char * Bonita Montero <Bonita.Montero@gmail.com> - 2019-09-11 11:37 +0200
        Re: standard error messages in a std::string or in a const char * Keith Thompson <kst-u@mib.org> - 2019-09-11 02:37 -0700
          Re: standard error messages in a std::string or in a const char * Bonita Montero <Bonita.Montero@gmail.com> - 2019-09-11 11:47 +0200
            Re: standard error messages in a std::string or in a const char * Öö Tiib <ootiib@hot.ee> - 2019-09-11 04:43 -0700
              Re: standard error messages in a std::string or in a const char * James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-09-11 08:27 -0400
                Re: standard error messages in a std::string or in a const char * Manfred <noname@add.invalid> - 2019-09-11 14:56 +0200
                Re: standard error messages in a std::string or in a const char * Daniel <danielaparker@gmail.com> - 2019-09-11 07:00 -0700
          Re: standard error messages in a std::string or in a const char * Thiago Adams <thiago.adams@gmail.com> - 2019-09-11 09:44 -0700
          Re: standard error messages in a std::string or in a const char * Jorgen Grahn <grahn+nntp@snipabacken.se> - 2019-09-12 10:21 +0000
            Re: standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-12 13:05 +0200
        Re: standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-11 17:43 +0200
          Re: standard error messages in a std::string or in a const char * Paavo Helde <myfirstname@osa.pri.ee> - 2019-09-11 19:23 +0300
            Re: standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-11 19:19 +0200
              Re: standard error messages in a std::string or in a const char * Paavo Helde <myfirstname@osa.pri.ee> - 2019-09-11 20:32 +0300
                Re: standard error messages in a std::string or in a const char * Soviet_Mario <SovietMario@CCCP.MIR> - 2019-09-12 13:08 +0200
                Re: standard error messages in a std::string or in a const char * Thiago Adams <thiago.adams@gmail.com> - 2019-09-12 04:29 -0700
                Re: standard error messages in a std::string or in a const char * Keith Thompson <kst-u@mib.org> - 2019-09-12 14:41 -0700
              Re: standard error messages in a std::string or in a const char * Thiago Adams <thiago.adams@gmail.com> - 2019-09-11 10:39 -0700
              Re: standard error messages in a std::string or in a const char * James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-09-11 19:50 -0400
                Re: standard error messages in a std::string or in a const char * Keith Thompson <kst-u@mib.org> - 2019-09-11 17:11 -0700
                Re: standard error messages in a std::string or in a const char * James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-09-11 20:23 -0400
                Re: standard error messages in a std::string or in a const char * David Brown <david.brown@hesbynett.no> - 2019-09-12 11:21 +0200
                Re: standard error messages in a std::string or in a const char * James Kuyper <jameskuyper@alumni.caltech.edu> - 2019-09-12 07:31 -0400
                Re: standard error messages in a std::string or in a const char * Manfred <noname@add.invalid> - 2019-09-12 15:44 +0200

csiph-web