Hi , I have modified of gcc to output XML equivalent of a program's GIMPLE IR.
I am also interested in knowing some of the things Alan is looking for : best practices, naming conventions for the XML output, policy on use of elements vs. attributes etc Regards, Karthiik On 10/11/07, Alan Conway <[EMAIL PROTECTED]> wrote: > I'm interested in getting hold of a C++ parser to analyse the use of > types and #include statements in C++, I'd hoped gccxml was it but then > stubbed my toe on the fact that types used inside functions aren't > dumped. > > I'd be interested in adding that if I can find the time. Can anyone give > me some pointers as to where I would need to make changes? Also any tips > on best practices, naming conventions for the XML output, policy on use > of elements vs. attributes etc. would be most appreciated. > > No promises I'll every actually do anything but I've already scripted up > half of the analysis based on gccxml output so I'm somewhat motivated to > finish the job. > > Cheers, > Alan. > > _______________________________________________ > gccxml mailing list > [email protected] > http://www.gccxml.org/mailman/listinfo/gccxml > -- Karthik **************************************************************************** To laugh often and love much; to win the respect of intelligent persons and the affection of children; to earn the approbation of honest critics; to appreciate beauty; to give of one's self; to leave the world a bit better, whether by a healthy child, a garden patch or a redeemed social condition; to have played and laughed with enthusiasm and sung with exultation; to know even one life has breathed easier because you have lived--that is to have succeeded. --Ralph Waldo Emerson **************************************************************************** _______________________________________________ gccxml mailing list [email protected] http://www.gccxml.org/mailman/listinfo/gccxml
