Hello. So i thought about it and come back to apologize. At least mildly. I guess the right thing to do would be to strip all paths which are also in the system array from the user paths present in the non-standardized $C_INCLUDE_PATH environment variable, even if that means that this possibly changes the search order desired by the user anyway. Or the approach of hell, use a token and once that is seen first, "temporarily rewind to global scope" and inject the necessary typedef there, or simply generate builtin knowledge of the type as such, not backed with anything a user can see when looking through the headers. I for one do not like any of those, not even the first, though.
--steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
