Talk:Precompiled header
![]() | Computing Unassessed | |||||||||
|
![]() | This article may be too technical for most readers to understand. |
Could someone list what they think is too technical? —kotepho 2006-03-19 18:47Z
- This article looks ok to me but then im a programmer, so it all makes sense to me. Not sure why the article itself is flagged as needing an expert, all the info looks correct. -Mloren 07:23, 1 August 2006 (UTC)
It's an ok article, although for some reason it insists more on the problems than the advantages. Someone who does not know how to program would not understand it though. The word compile is not explained even. --Jackaranga 13:26, 4 March 2007 (UTC)
Changes I made
Just made some changes to the article to (hopefully) improve the grammar, clarity and especially to make it more accessible to non-technical users. The final sections are specific to the compilers and I am afraid are beyond me (while I am a programmer, I am not a programmer of C or C++). I have tagged it for attention of a C/C++ expert who can with any luck improve the later sections. MrWeeble Talk Brit tv 13:53, 5 March 2007 (UTC)
--
The comment: "there is a chance for slowing down compilation if too much unused code is contained into the headers" seems innacurate to me, and I would like to see some data supporting/define the cases where this would occur. In my experience, I have never seen or worked on a project where this is the case. And, apart from pathelogical cases designed specifically to achieve this goal, it's hard for me to even imagine a scenario that wouldn't benefit compilation speed-wise from using precompiled headers (ie 1 file that uses all the info in the PCH and then 1000 files that use 1 decalration from the PCH).
Secondly, "the results of subdividing the source code are often far better than one could possibly achieve with precompiled headers", doesn't make sense to me. PCHs and dependency reduction are two orthogonal methods of achieving compilation time speedup. If you take your perfectly subdivided code and apply PCHs properly, your (non-pathelogical) project will compile faster (and vice versa). --Greysphere 01:46, 17 May 2007 (UTC)
Merge of 20070629
Some rv performed. Rationale:
- Try to merge newer version (which explicits that "stdafx.h is generated by Microsft Visual Studio IDE wizards") with previous one (from which some information was removed). Result:
- Keep original paragraph, avoid 2nd person
- Restore third paragraph, which was partially merged with second one. Information kept from both versions.