On 1/14/2011 10:17 AM, Achilleas Margaritis wrote:
The #autoinclude pragma can select to inline only those member functions that are good candidates for inlining. I.e. it can inline trivial code. I believe the GCC code already contains such criteria, like any other good compiler.
Not sure what you are suggesting here, it is only deep in the back end code generation that the decision can be made as to whether something is a good candidate for inlining. How does that help you?
There is a lot of resistance to this idea, I admit; but I haven't seen any concrete argument about why my proposal is not good. It seems the resistance comes in two flavors: 1) It is not interesting work for me, so you do it or pay someone else to do it (you seem to be into that camp).
That's always an appropriate response! The remedy is to propose a patch yourself (or pay someone to do it), then we can see if it makes sense when the details are worked out.
2) I like headers because they are specifications (they aren't, but what can I do if one believe so? nothing). Hey, at least I tried :-).
