🚀 go-pugleaf

In article <l8220qk4oos.fsf@neppari.cs.hut.fi> Lassi.Tuura@hut.fi (Lassi A. Tuura) writes:

> I see two possible paths emerging from the current situation:
>   - programmers put "using namespace std;" in their programs, which
>     will be *very* unfortunate; it will be hard to motivate them
>     not to do so, at least not until the next revision is made to the
>     standard and they have tons of clashes...

Even if programmers do put "using namespace std" in their programs,
that isn't necessary such a disaster.  Remember, you can put a
using-directive anywhere, not just at namespace scope.  So you can put
"using namespace std" in function definitions (and not necessarily all
function definitions), rather than at the beginning of every file.
That will ensure, at any rate, that any problems will be local ones.

I agree that it would be nice to have namespace std partitioned a bit
more finely; I doubt if it will happen, though.  Coming up with a
sensible partitioning might be a fair amount of work.
-- 
  Matt Austern                             He showed his lower teeth.  "We 
  matt@physics.berkeley.edu                all have flaws," he said, "and 
  http://dogbert.lbl.gov/~matt             mine is being wicked."

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]