I agree, this was done before it was considered bad form to do so;
especially in header files. I suppose it really depends on how many cc
files exploited this. Of course, it's easy to figure out.

On Wed, 22 Feb 2023, Guilherme Amadio wrote:

> We will need to get rid of this before moving to C++17:
>
> ```
> $ git grep 'using namespace std' | grep \.hh
> src/XrdOuc/XrdOucString.hh:using namespace std;
> src/XrdSys/XrdSysHeaders.hh:using namespace std;
> ```
> I will give it a try, but it may require lots of changes.
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1929#issuecomment-1441312378
> You are receiving this because you are subscribed to this thread.
>
> Message ID: ***@***.***>


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/pull/1929/c1441320946@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1929#issuecomment-1441320946", "url": "https://github.com/xrootd/xrootd/pull/1929#issuecomment-1441320946", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1