all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: "Taylan Ulrich Bayırlı/Kammer" <taylanbayirli@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Some macros to make package definitions prettier
Date: Wed, 25 Feb 2015 12:06:31 -0500	[thread overview]
Message-ID: <CAJ=RwfYt=vm6wVF1Ku+tgYHXdkLuSAWg=TzAYLbgjhNNnOWwJA@mail.gmail.com> (raw)
In-Reply-To: <CAJ=RwfaVe-7Q5gV-487NeWD_TBhiWZA8jrUaeyhoo12yXZV8ZA@mail.gmail.com>

On Wed, Feb 25, 2015 at 12:04 PM, Thompson, David
<dthompson2@worcester.edu> wrote:

> I understand the temptation to name it 'modify-phases', but since this
> macro applies to any alist, I think 'modify-alist' or something with
> "alist" in the name would be more appropriate.

Looking again, I see that the above isn't quite true.  The
'modify-phases' macro assumes that the keys of the alist are symbols
so that the user doesn't have to quote the phase names.

- Dave

  reply	other threads:[~2015-02-25 17:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 16:42 Some macros to make package definitions prettier Taylan Ulrich Bayırlı/Kammer
2015-02-25 17:04 ` Thompson, David
2015-02-25 17:06   ` Thompson, David [this message]
2015-02-25 19:27     ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 20:54   ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 18:12 ` Andreas Enge
2015-02-25 19:46   ` Taylan Ulrich Bayırlı/Kammer
2015-02-25 20:24   ` Thompson, David
2015-02-25 23:32 ` Ludovic Courtès
2015-02-26 11:07   ` Taylan Ulrich Bayırlı/Kammer
2015-02-26 21:39     ` Ludovic Courtès
2015-03-03 16:49       ` Taylan Ulrich Bayırlı/Kammer
2015-03-03 20:44         ` Ludovic Courtès
2015-03-03 22:47           ` Taylan Ulrich Bayırlı/Kammer
2015-03-04  9:52             ` Ludovic Courtès
2015-02-26 21:41     ` 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

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

  git send-email \
    --in-reply-to='CAJ=RwfYt=vm6wVF1Ku+tgYHXdkLuSAWg=TzAYLbgjhNNnOWwJA@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=taylanbayirli@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.