🚀 go-pugleaf

In article <VANDEVOD.95Oct13185849@avs.cs.rpi.edu>,
vandevod@cs.rpi.edu (David Vandevoorde) wrote:

|> Vaguely related: say I want to pull everything that has to do with 
|> valarrays (more precisely: all the classes and functions described 
|> (in 26.3)) in my program, but I'd rather not pull in all of ::std.
|> (And I don't want to issue dozens of `using's either.)

At one point the Library WG considered multiple nested namespaces for this
purpose. They backed off, I think because of problems with operator lookup
(amongst others). Now that the operator lookup is 'fixed' it would probably
be a good idea to revisit the partitioning of the library.

In answer to your question, you could synthesise your own namespaces
containing just those elements you wanted but it would be somewhat
laborious:

namespace std_valarray {
  using std::valarray;
  using std::...
  // etc etc etc
}

Then the std_valarray namespace would provide what you want.




[ 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. ]