Hi Danushka, > > To be pedantic if you have "using qpid::framing" then this tells the > > compier that any unqualified reference to "framing" is actually a > > reference to "qpid::framing" so you can't remove the "framing::" > > prefixes. ["using qpid::framing" == namespace framing = > qpid::framing" > > in this context] > > > > > Andrew, > > I dont think you can have "using qpid::framing" but "using /namespace > /qpid::framing" as qpid::framing is not a symbol but a namespace.
Right. After working a bit more on this, this is what I'd like to do: - Not put in a blanket "using namespace qpid" - I agree that's too far. - Use, for example, "namespace framing = qpid::framing" as Andrew mentions above. Then the existing framing::... works on both g++ and MSVC. Also, a guideline I'd like to see, and would like to hear more from you all, is to always have some sort of namespace tag on classes that are outside the namespace being worked on. For example, I was looking at qpid/management/ManagementBroker.cpp - it refers to classes from framing and broker as well. I'd like those to be explictly referred to, such as: namespace broker = qpid::broker; namespace framing = qpid::framing; ... framing::Buffer buff; ... Otherwise newbies like me have no clue where all these classes are coming from. With the namespaces I have a good starting point for where to look for more info on the class in question. -Steve
