| Date: | Mon, 25 Apr 2016 10:05:41 -0700 |
|---|---|
| From: | Josh Stone <jistone@xxxxxxxxxx> |
| Subject: | Re: [DynInst_API:] [PATCH 1/2] Reduce namespace pollution |
On 04/23/2016 12:57 PM, Peter Foley wrote: > Don't unconditionally include all of namespace std I agree it's good practice avoid "using namespace std;" in API headers, so you don't force that on the library's users. However, IMO removing std from all the source files is needless churn. It's perfectly fine for a project to unconditionally use std internally as many projects do, and as dyninst has for a long time. Is there a real problem you're trying to solve here? |
| [← Prev in Thread] | Current Thread | [Next in Thread→] |
|---|---|---|
| ||
| Previous by Date: | Re: [DynInst_API:] Slicing across blocks, Mohamed Elsabagh |
|---|---|
| Next by Date: | Re: [DynInst_API:] [PATCH 1/2] Reduce namespace pollution, Peter Foley |
| Previous by Thread: | [DynInst_API:] [PATCH 2/2] fix more namespace pollution, Peter Foley |
| Next by Thread: | Re: [DynInst_API:] [PATCH 1/2] Reduce namespace pollution, Peter Foley |
| Indexes: | [Date] [Thread] |