Christopher Li wrote:
Hi Konrad, I appreciate all the input. How about this, I am going to implement the core sparse part of the API change. You will be the first customer that use that API. I think this API is also useful for people want to do source code transformations using sparse. They usually want to manipulate the source code stream before the pre-processing. Anyway, I am hacking a branch starting from the last patch I send out. I am adding the test program to demonstrate how to use those hooks to accomplish different things. You just need to keep telling me what extra feature you want from the API. I can try to incorporate them with the demo program.
Yea, I think it is better that way. You should implement it yourself first, it kind of takes too long otherwise :-). Still I'm kind of curious how you can trace macro expansion with just 1 callback but I'll like to be surprised. -- Konrad
I will let you know when I have the branch ready. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
-- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
