From: pete@versatilecoding.com   
      
   On 2012-04-14 18:27:02 +0000, Pete Becker said:   
      
   > On 2012-04-13 22:28:09 +0000, James K. Lowden said:   
   >   
   >> I would guess the commmittee's intention was to make the std   
   >> namespace *standard* and thus predictable on inspection.   
   >   
   > Not so much. Mostly it means you can count on it being there. Library   
   > implementors can take liberties with how they define things under the   
   > as-if rule: if a conforming program can't detect a difference, it's   
   > okay. So a library vendor can add identifiers to std pretty much   
   > without risk, because a conforming program won't use those   
   > identifiers.   
      
   Whoops, posted too early in the morning. A conforming program can   
   detect names like "foo" that implementors add to namespace std by the   
   ugly and counterproductive "using namespace std". Just beause it's bad   
   code doesn't mean it's illegal.   
      
   --   
      Pete   
   Roundhouse Consulting, Ltd. (www.versatilecoding.com) Author of "The   
   Standard C++ Library Extensions: a Tutorial and Reference   
   (www.petebecker.com/tr1book)   
      
      
         [ See http://www.gotw.ca/resources/clcm.htm for info about ]   
         [ comp.lang.c++.moderated.    First time posters: Do this! ]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)