From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA] Clean up coding standards, add python coding standards.
Date: Tue, 19 Oct 2010 18:45:00 -0000 [thread overview]
Message-ID: <83bp6q9g4r.fsf@gnu.org> (raw)
In-Reply-To: <20101019155311.038842461AD@ruffy.mtv.corp.google.com>
> Date: Tue, 19 Oct 2010 08:53:10 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> I think it is wrong that a discussion of cleanups appears in the same
> chapter as coding standards. Ditto for a few other subsections
> in the existing Coding chapter.
>
> This patch creates a new Coding Standards chapter to put such things in,
> and I've added a section on Python coding standards.
Thanks.
> I'm not happy with the name "Miscellaneous Coding Guidelines" but it
> works well enough for me. Feel free to suggest an alternatives.
"Misc Guidelines"? In general, node names should be short, because
they are displayed on the mode line and header line of the Info
readers, where space is at premium. (Section names, OTOH, can be
longer.)
> Ok to check in?
Could you tell me if you made any changes in the "Internal Error
Handling" part, or just moved it without any changes? If you just
moved it, I won't need to review that part.
> -* Coding::
> +* Miscellaneous Coding Guidelines::
> +* Coding Standards::
I think "Coding Standards" should be before the new "Misc" section.
> +@value{GDBN} follows the published @code{Python} coding standards in
> +@code{PEP008}.
> +See @uref{http://www.python.org/dev/peps/pep-0008/, PEP008}.
This is suboptimal usage of @uref. I suggest this instead:
@value{GDBN} follows the published @code{Python} coding standards in
@uref{http://www.python.org/dev/peps/pep-0008/, @code{PEP008}}.
> +In addition, the Google standards are also followed where they do not
> +conflict with @code{PEP008}.
> +See @uref{http://google-styleguide.googlecode.com/svn/trunk/pyguide.html,
> +Google Python Style Guide}.
Same here:
In addition, the guidelines in the
@uref{http://google-styleguide.googlecode.com/svn/trunk/pyguide.html,
Google Python Style Guide} are also followed where they do not
conflict with @code{PEP008}.
Okay with those changes (assuming that the "Internal Error Handling"
stuff was moved without any change).
Thanks for taking care of this.
next prev parent reply other threads:[~2010-10-19 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 15:53 Doug Evans
2010-10-19 18:45 ` Eli Zaretskii [this message]
2010-10-20 22:56 ` Doug Evans
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=83bp6q9g4r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.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