A. Litman; "An Implementation of Precompiled Headers" in Software - Practice and Experience, 23:3, March 1993, pp. 341-350.  Home/Search   Document Details and Download   Summary   Related Articles

.... very low level tool, its significance has been mentioned in workshops on software configuration management [SCM] Win88] Sch89] Gen89] Malh94] and on software reuse [Gro93] Problems due to its use have also been reported for large software products [Spe92] Til92] Some tools have been developed [Lit93] [Vo92] Recently, different, independent research have shown a growing interest in CPP, taking it as a case study or seeing it from a reengineering point of view [Spu92] Mun93] Sin93] Fav93] Kro94] Liv94] Zel94] Fav94] Sne95] Fav95] 1. While PITS deals with programs, PITL deals with ....

....which these include files have been included. This solution is not reliable and X should itself include these files by means of #include directives. In this case an include file can be processed more than once. Giving such output to a compiler can lead to significant performance decreases [Vo92] [Lit93] and to compilation errors if multiple definitions are not allowed by the language. To cope with this problem a common practice consist to use a sequence #ifndef aname #define aname filecontent #endif [Spe92] The file content will appear only once in the output. CPP, parametrisation and ....

A. Litman; "An Implementation of Precompiled Headers" in Software - Practice and Experience, 23:3, March 1993, pp. 341-350.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC