[LLVMdev] [RFC] New ToolsSupport library for stuff that only tools need

Reid Kleckner rnk at google.com
Thu Nov 6 15:43:11 PST 2014


On Thu, Nov 6, 2014 at 3:22 PM, Chris Bieneman <beanz at apple.com> wrote:
>
> The other thought I had which motivated this solution was that if we could
> strip all the functionality that is only really used by tools out into a
> separate library it would offer cleaner organization of code. Support seems
> to often get used as a dumping ground for stuff that just doesn’t fit
> anywhere else.
>


> Based on your feedback and Chandler’s maybe this just isn’t the right
> separation. I can look into a solution to address our hackiness without
> creating a separate library.
>

What other stuff do you think belongs in ToolsSupport that doesn't belong
in Support? Looking back at the initial email, you have command line
parsing and ToolOutputFile.

We could split out command line parsing, but it doesn't seem worth it,
given that we're still carrying regex support, Unicode conversion, dynamic
library support, and other things that probably aren't absolutely necessary.

What about splitting out a CrashRecovery library instead? That seems a lot
more targeted and meaningful. We'd probably put ToolOutputFile.cpp in there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141106/9ed05a11/attachment.html>


More information about the llvm-dev mailing list