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: Fri, 27 Aug 2010 08:16:33 -0700	[thread overview]
Message-ID: <m3fwy0gk6m.fsf@unquote.localdomain> (raw)
In-Reply-To: <8762yw8nn5.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Fri, 27 Aug 2010 10:29:02 +0200")

Hi Thien-Thi,

Let me say first that I am really happy to have your energetic,
experienced hand going over Guile sources. Thank you! I do think that
small things are important, and your willingness to look at the small
*and* the big is much appreciated. It's nice to have thoughtful, local
commits.

On Fri 27 Aug 2010 01:29, Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> I will avoid general cleanup, but i don't intend to avoid cleanup on
> files i wish to hack on (for now, this set includes makefiles, build
> scripts and documentation).

Fair enough. Please continue to separate cleanup commits from other
commits.

> I sidestepped [issues in guile-func-name-check], by rewriting in
> Scheme (and using Emacs' ‘indent-sexp’).  Unfortunately, it looks like
> hydra is not liking it:
>
> http://hydra.nixos.org/build/606792
>
> Perhaps a workaround would be to use ‘--no-autocompile’ in the
> invocation command (libguile/guile-snarf-docs.in:55), but that seems
> ugly and throws away a bug-{hunt,squash}ing opportunity.  WDYT?

I think that not autocompiling is the right thing in this case. We don't
actually want to autocompile in Guile when, um, compiling :)

Also in the future, please run clean builds when you change invocations
of guile within libguile/.  Thanks :)

> Another related idea: Since Guile supports many languages, why not AWK?

That would be fun!

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-08-27 15:16 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
2010-07-02 13:14   ` Ludovic Courtès
2010-08-27  8:29   ` Thien-Thi Nguyen
2010-08-27 15:16     ` Andy Wingo [this message]
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=m3fwy0gk6m.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).