search for: versionprint

...ould be quite convenient to be able to dynamically determine the  > version that happens to be loaded. > > Honestly, I am not completely clear on what the best place for  > something like this would be, but it appears that the following seems  > like a natural choice: > > llvm::VersionPrinter in lib/Support/CommandLine.cpp already queries  > this data so it might make sense for it to expose the following API's  > (as part of VersionPrinter, accessed through the instance): > llvm::cl::getVersionMajor() > llvm::cl::getVersionMinor() > llvm::cl::getVersionPatch() Hi,...

...version that happens to be loaded. > > > > > > Honestly, I am not completely clear on what the best place for  > > > something like this would be, but it appears that the following > > seems  > > > like a natural choice: > > > > > > llvm::VersionPrinter in lib/Support/CommandLine.cpp already > > queries  > > > this data so it might make sense for it to expose the following > > API's  > > > (as part of VersionPrinter, accessed through the instance): > > > llvm::cl::getVersionMajor() > > > llvm::...

...;>> > >>>> Honestly, I am not completely clear on what the best place for > >>>> something like this would be, but it appears that the following > >>> seems > >>>> like a natural choice: > >>>> > >>>> llvm::VersionPrinter in lib/Support/CommandLine.cpp already > >>> queries > >>>> this data so it might make sense for it to expose the following > >>> API's > >>>> (as part of VersionPrinter, accessed through the instance): > >>>> llvm::cl::getV...

...gt;>> Honestly, I am not completely clear on what the best place for >> >>>> something like this would be, but it appears that the following >> >>> seems >> >>>> like a natural choice: >> >>>> >> >>>> llvm::VersionPrinter in lib/Support/CommandLine.cpp already >> >>> queries >> >>>> this data so it might make sense for it to expose the following >> >>> API's >> >>>> (as part of VersionPrinter, accessed through the instance): >> >>&gt...