On Monday 14 of September 2009 22:47:40 Christopher Li wrote: > Can you clarify why do you need to use the UID instead of the pointer of > symbol? One reason I can see is that if you want to dump the AST tree > into objects on disk. Other application can read it back and load into > memory. If the symbol already exist in the memory, you should be able to > use pointer directly. The only reason (for now) is that I already use them with the gcc plug-in and the code_listener interace is based on them. I don't think it *needs* to be implemented in SPARSE since the workaround is easy. I've only raised the idea in hope such enumeration might be generally useful. Adding Petr Peringer to CC. He came with UID idea to our project and might be able to give us better clarification for that approach. > BTW, I have code to dump most of the struct into disk already. I think > I send to the list before. Of course I can create a branch for it. Reading > is not completed yet. Thanks! Good to know something like that is available. But I don't think our project can gain from this functionality right now. Kamil -- 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
