unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCHES] various commenting, whitespace changes
Date: Mon, 28 Jun 2010 15:44:54 +0200	[thread overview]
Message-ID: <m3y6dzxodl.fsf@unquote.localdomain> (raw)
In-Reply-To: <87bpazfgsq.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Fri, 25 Jun 2010 14:16:53 +0200")

Hello,

On Fri 25 Jun 2010 14:16, Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> From 9c6b71e9b3334439ae6348b38412ae6a8fb154ad Mon Sep 17 00:00:00 2001
> Subject: [PATCH 3/8] Comment, whitespace munging; nfc.

What does NFC mean?

In general I'm a little uneasy with this kind of change, as it is
unnecessary. But, OK, I guess. Please feel free to make files more
closely follow GNU conventions, when you are working on those files; but
do avoid a general cleanup. I think it would drive me crazy ;) Perhaps
Ludovic will chime in later with more general feedback.

> --- a/libguile/guile-func-name-check
> +++ b/libguile/guile-func-name-check
[...]
>  BEGIN {
> -  filename = ARGV[1];
> -  in_a_func = 0;
> +    filename = ARGV[1];
> +    in_a_func = 0;
>  }

There is no need to change the indentation amount here; 2-space should
be fine.

[...]
> +# guile-func-name-check ends here

I would rather not have these markers. It's an extra point of bitrot.

If you really want the end-of-file markers I would want some
confirmation from Ludovic; otherwise, I am OK with you pushing these
patches without the EOF markers and without changing the awk script
indentation.

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-06-28 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-25 12:16 [PATCHES] various commenting, whitespace changes Thien-Thi Nguyen
2010-06-28 13:44 ` Andy Wingo [this message]
2010-07-02 13:14   ` Ludovic Courtès
2010-08-27  8:29   ` Thien-Thi Nguyen
2010-08-27 15:16     ` Andy Wingo
2010-08-27 20:15       ` Andy Wingo
2010-08-27 21:42         ` Thien-Thi Nguyen

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=m3y6dzxodl.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ttn@gnuvola.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).