Reid Kleckner via llvm-dev
llvm-dev at lists.llvm.org
Tue Apr 19 08:47:34 PDT 2016
Honestly I don't know if I would recommend using libOption or cl::opt if
you're making a new tool with a new command line interface.
libOption evolved out of Clang, and its primary goal was to parse GCC-style
command lines, which don't follow the rules of cl::opt. We reused it for
LLD since it has similar parsing issues, but if you don't have those
challenges, it's kind of heavyweight. Oh, and our usage of it is generally
O(n^2) in the command line length, because finding the last flag is linear (
cl::opt encourages global options, which has been a mixed blessing and
On Tue, Apr 19, 2016 at 5:47 AM, Russell Wallace via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> I'm given to understand that the recommendation these days is to use
> libOption instead of cl::opt, on the grounds that it has a number of
> advantages including more control of which options are made available.
> Is there any information available on how to use libOption, any
> documentation or example programs? Do any existing programs use it except
> the clang driver programs? Those customise their commandline handling
> heavily enough that it's hard to use them as examples.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev