unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [PATCH] ui: Add a 'define-diagnostic' macro.
Date: Sat, 20 Apr 2013 11:09:28 +0200	[thread overview]
Message-ID: <87r4i5bmbb.fsf@gnu.org> (raw)
In-Reply-To: <8761zie0nz.fsf_-_@karetnikov.org> (Nikita Karetnikov's message of "Sat, 20 Apr 2013 00:16:32 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>> This is a macro-generating macro.  In the body of the generated macro,
>> above, there are 4 occurrences of ‘...’.  But these ellipses have no
>> meaning in the outer macro; they are just meaningful in the context of
>> the generated macro, hence the error.
>
>> Instead, you should replace all 4 occurrences with (... ...).
>
>> Yes, it’s always surprising at first.  ;-)
>
> Yep, could you add it to the manual?  There is only a reference to this
> book [1] which briefly discusses the topic.

Well, it’s specified in R[56]RS I believe, but yeah.

> I'm attaching the patch that adds a 'define-diagnostic' macro.  Can I
> push it to 'master'?

Looks good to me.  Make sure to run ‘make clean && make’ before, to see
if there’s anything that fails to build (you only need to do this
because these are macros.)

> I ran 'grep' to find things which use "warning" or "leave."  I guess
> it's possible to change other functions (the ones that use 'error' and
> 'format').  But it will probably trigger a rebuild.  So what should I
> do?

Everything in guix/build/* must be left as is: it’s not part of the UI,
except perhaps for (guix build download).  However, the rule is to only
import (guix build ...) modules in (guix build ...) modules.

So this looks fine as is.  We’ll see later if there’s anything wrong
with (guix build download) or something else.

> Also, is it possible to move 'report-error' inside 'leave'?

Didn’t you want to export it as well?  But otherwise no.

> Finally, I haven't tested each change.  All tests pass and there are no
> warnings.  Is it good enough?

Plus ‘make clean && make’.

Please push if it passes that.

Thanks!

Ludo’.

  parent reply	other threads:[~2013-04-20  9:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-01  5:06 [PATCH] Add 'guix hash' Nikita Karetnikov
2013-04-03  8:34 ` Ludovic Courtès
2013-04-05 14:04   ` Nikita Karetnikov
2013-04-05 14:14     ` Nikita Karetnikov
2013-04-05 16:15       ` Ludovic Courtès
2013-04-10 11:48         ` Nikita Karetnikov
2013-04-10 11:54           ` Ludovic Courtès
2013-04-10 12:21             ` Nikita Karetnikov
2013-04-10 17:30               ` Ludovic Courtès
2013-04-05 16:13     ` Ludovic Courtès
2013-04-09 16:28       ` Nikita Karetnikov
2013-04-11 20:35         ` Ludovic Courtès
2013-04-12  5:24           ` master: FAIL: tests/guix-package.sh (was: [PATCH] Add 'guix hash'.) Nikita Karetnikov
2013-04-12  6:48             ` master: FAIL: tests/guix-package.sh Nikita Karetnikov
2013-04-12 16:24             ` Ludovic Courtès
2013-04-18  5:01       ` Enhanced 'warning' (was: [PATCH] Add 'guix hash'.) Nikita Karetnikov
2013-04-18  5:06         ` Enhanced 'warning' Nikita Karetnikov
2013-04-18 11:55         ` Ludovic Courtès
2013-04-18 19:27           ` Nikita Karetnikov
2013-04-18 20:59             ` Ludovic Courtès
2013-04-19 20:16               ` [PATCH] ui: Add a 'define-diagnostic' macro. (was: Enhanced 'warning') Nikita Karetnikov
2013-04-20  5:48                 ` [PATCH] ui: Add a 'define-diagnostic' macro Nikita Karetnikov
2013-04-20  9:10                   ` Ludovic Courtès
2013-04-20 17:33                     ` Nikita Karetnikov
2013-04-20 19:55                       ` Ludovic Courtès
2013-04-20  9:09                 ` Ludovic Courtès [this message]
2013-04-21 18:14       ` [PATCH] Add 'guix hash' Nikita Karetnikov
2013-04-21 19:02         ` Ludovic Courtès

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87r4i5bmbb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).