public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Björn Schäpers" <gcc@hazardy.de>
To: Jonathan Wakely <jwakely@redhat.com>,
	Dimitrij Mijoski <dmjpp@hotmail.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Subject: Re: Add clang-format for libstdc++
Date: Wed, 8 Feb 2023 21:04:48 +0100	[thread overview]
Message-ID: <bc3796c6-0d94-7973-0cae-4dec78588266@hazardy.de> (raw)
In-Reply-To: <CACb0b4=kL=w-0z30emQAnhCpWwN7EzTc16gG3Bc=gQ5Or2doaQ@mail.gmail.com>

Am 07.02.2023 um 22:17 schrieb Jonathan Wakely via Libstdc++:
> On Tue, 7 Feb 2023 at 20:39, Dimitrij Mijoski via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>>
>> Is there interest to add a clang-format file for libstdc++?
>>
>> The basic idea is to take the existing clang format located at contrib/clang-format,
>> copy it to contrib/clang-format-libstdc++, and modify it according to libstdc++ rules
>> https://gcc.gnu.org/onlinedocs/libstdc++/manual/source_code_style.html .
>> Similarly to the first clang-format, it will be optional and it will be enabled if the developer
>> calls the command:
>>
>> make clang-format
>>
>> inside the build tree. That will create the symbolic link srcdir/libstdc++-v3/.clang-format .
>> Alternatively, it can be put directly where it is required without the need for the invocation
>> of make.
> 
> If you want to do the work and contribute it, please go ahead. But
> last time somebody looked into it, clang-format doesn't support our
> code style conventions. There was something in our template
> indentation that clang-format doesn't support, and can't be configured
> to support.
> 

As someone who develops on clang-format: That could be changed.

      reply	other threads:[~2023-02-08 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 20:38 Dimitrij Mijoski
2023-02-07 21:01 ` Thomas Rodgers
2023-02-07 21:19   ` Jonathan Wakely
2023-02-07 21:24     ` Thomas Rodgers
2023-02-10 22:05   ` Stephan Bergmann
2023-02-10 23:02     ` Jonathan Wakely
2023-02-13 10:18       ` Stephan Bergmann
2023-02-07 21:17 ` Jonathan Wakely
2023-02-08 20:04   ` Björn Schäpers [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc3796c6-0d94-7973-0cae-4dec78588266@hazardy.de \
    --to=gcc@hazardy.de \
    --cc=dmjpp@hotmail.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).