Hello Christian, >> There was a request that shared library should automatically load >> all the standard header files loaded in the precompiled header file. >> >> All the files started by '<' are standard header files to be loaded >> with the shared library. This is intentional. > >I'm not convinced this is generally true. I like to compile my libs, >etc, using the `-I./' switch (using GCC ofcourse), and exclusively use >the `#include <...>' preprocessor derictive. Even you use the >directive `#include "..."' for the user headers, you may include >header files with `#include <...>' which isn't standard headers in a >strict sense. E.g., you may include the ROOT header `#include ><Rtypes.h>', but this really isn't a standard header (and ROOT already >knows the declerations in this header). Sorry about my poor explanation. My original sentense brings completely different meaning. I used '<' as a private symbol to judge if that come from standard header directory. This happens in dictionary source code where normal user do not see. It is completely differentfrom #include <...>. >> I belive this is a good feature. So far, I have not found any side-effect, >> but potential risk is there. Please report me any problems. If you find >> one, define G__OLDIMPLEMENTATION1271 in G__ci.h to deactivate the feature. > >I disagree. I think it should be the responsoblility of the user, >rather then the programmer, to include the prober header files, as is >the case of normal developing. I understand your opinion. Maybe This feature should be provided as an option. >Anyway, that's my two cents worth. > >Oh, and let me take this oppertunity for complementing you on your >spectacular feat of creating CINT. Thanks a lot! Thank you for your remark. Masaharu Goto
This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:19 MET