home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.lang.c++.moderated      Moderated discussion of C++ superhackery      33,346 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 32,805 of 33,346   
   james.d.mclaughlin@googlemail.com to All   
   #include and #include    
   22 Jan 13 13:01:53   
   
   { Please limit your text to fit within 80 columns, preferably around 70,   
     so that readers don't have to scroll horizontally to read each line.   
     This article has been reformatted manually by the moderator. -mod }   
      
   I was having a look through the header files for a SAT-solver that I   
   needed to work out how to use, and which for some reason seemed to be   
   using a lot of the C versions of the headers ( instead of   
    for instance) alongside C++ headers such as .   
      
   Which is how I encountered this:   
      
   #include    
   #include    
   #include    
      
   Does anyone know of any reason why someone would want to #include both   
   stdio.h and cstdio in the same file? More importantly, are there any   
   potential pitfalls to doing this? If there are, can I just fix them by   
   commenting out the line with stdio.h?   
      
   A slightly less important question as well - does anyone know of any   
   reason not to change  to  in the above? I can easily   
   go through the file putting std:: before function names and the like.   
      
   Many thanks,   
      
   James McLaughlin.   
      
      
   --   
         [ 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)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca