search for: printfileheaders

...it doesn't clash? I know windows.h is quite invasive, so maybe it's better not try to collide with any of its weird define. If that makes sense I'm fine with doing the patch. If yes, feel free to propose an alternative naming prefix or scheme. Note that if tools depend on COFFDumper::printFileHeaders output, it might still need to print as it was before -- so the easiest choice might be to maybe just drop the IMAGE_ (anyway it's in llvm::COFF so it shouldn't matter). Is it important? Thanks, Virgile -------------- next part -------------- An HTML attachment was scrubbed... URL: <htt...

...w windows.h is quite invasive, so maybe it's better not try to > collide with any of its weird define. > > If that makes sense I'm fine with doing the patch. > If yes, feel free to propose an alternative naming prefix or scheme. > > Note that if tools depend on COFFDumper::printFileHeaders output, it might > still need to print as it was before -- so the easiest choice might be to > maybe just drop the IMAGE_ (anyway it's in llvm::COFF so it shouldn't > matter). Is it important? > > Thanks, > Virgile > > _______________________________________________...

...asive, so maybe it's better not try to >> collide with any of its weird define. >> >> If that makes sense I'm fine with doing the patch. >> If yes, feel free to propose an alternative naming prefix or scheme. >> >> Note that if tools depend on COFFDumper::printFileHeaders output, it >> might still need to print as it was before -- so the easiest choice might >> be to maybe just drop the IMAGE_ (anyway it's in llvm::COFF so it shouldn't >> matter). Is it important? >> >> Thanks, >> Virgile >> >> ________________...