[cfe-commits] [cfe-dev] Announcing an official home for tools built on the Clang platform, as part of the Clang project

[Chandler Carruth]

On Tue, Aug 14, 2012 at 11:29 AM, Manuel Klimek <klimek at google.com> wrote:

> On Tue, Aug 14, 2012 at 8:08 PM, Marshall Clow <mclow.lists at gmail.com>
> wrote:
> > On Aug 14, 2012, at 10:54 AM, Chandler Carruth <chandlerc at google.com>
> wrote:
> >
> > On Tue, Aug 14, 2012 at 10:49 AM, David Blaikie <dblaikie at gmail.com>
> wrote:
> >>
> >> On Tue, Aug 14, 2012 at 10:33 AM, Chandler Carruth <
> chandlerc at google.com>
> >> wrote:
> >> > Can you call the tool 'template-tool' and 'TemplateTool'?
> >>
> >> (minor bikeshed, perhaps) - "template tool" sounds like it's a tool
> >> for doing something to templates. Perhaps "tool template" or "tool
> >> skeleton" (I would think "example" would be less ambiguous - but
> >> examples tend to actually do something, so I can see why that might
> >> not be preferred)
> >
> >
> > I'm fine with anything that is generic and clear: it shouldn't appear to
> be
> > specifically about refactoring, and it should clearly be for use in
> copying,
> > and stuffing your custom code in.
> >
> > I'll let others bike shed toward those goals.
> >
> >
> > sampleTool ?
> > sampleClangTool ?
> > toolTemplate?
> > clangToolTemplate?
>
> Throwing in my color preference: I like "template" in the name, as
> that's clearly meant to be something to copy from vs. sample which
> sounds more like something to learn from.
>
> So: 1 vote for clangToolTemplate


FWIW, I wasn't waffling on the casing. ;] The binary and directory should
be clang-tool-template, and the file should be ClangToolTemplate.cpp.

I have some distant hope of, once we have a proper collection of tools,
getting a git-like driver for the command line interfaces.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20120814/7491af49/attachment.html>