all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe <luis.felipe.la@protonmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: What's the meaning of the percent sign in variable names
Date: Sat, 24 Apr 2021 13:29:05 +0000	[thread overview]
Message-ID: <sGgo-0X_AALzpkUFEWwcN-2zcion_1_dGarMaVDiVMiUEipVKkcTOCXBVYhvEEwZhX77e4RWJ2LegHta4NW3JZ41a5wzbrEQ_CMuNN0ujhk=@protonmail.com> (raw)
In-Reply-To: <0567efc70b7282ff6f40173cba74a61ce2647644.camel@student.tugraz.at>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, April 23, 2021 2:49 PM, Leo Prikler <leo.prikler@student.tugraz.at> wrote:

> Am Freitag, den 23.04.2021, 14:22 +0000 schrieb Luis Felipe:
>
> > Hi,
> > Are all these constants (%base-packages, for example)? Is this a Guix
> > convention or does it come from Guile? Although looking at Guile's
> > Variable index I see many constants in uppercase, and also some
> > variables prefixed with the percent sign, while Guix' Programming
> > index doesn't seem to list any uppercase names.
>
> The tendency to prepend variables with % certainly comes from Guile or
> more generally Scheme. The upper case constants in Guile likely come
> from C, where this convention is more popular and IIUC often concerns
> integer constants, that are in some way important for the C side of
> things (think of stuff like OPEN_READ). Since that is not a concern
> for Guix, a package manager mostly written in Guile Scheme, we can
> prefix our constants with a percent sign.

Thanks, Leo.


  reply	other threads:[~2021-04-24 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 14:22 What's the meaning of the percent sign in variable names Luis Felipe
2021-04-23 14:49 ` Leo Prikler
2021-04-24 13:29   ` Luis Felipe [this message]
2021-05-04 15:49 ` Ludovic Courtès
2021-05-05 14:18   ` Luis Felipe

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='sGgo-0X_AALzpkUFEWwcN-2zcion_1_dGarMaVDiVMiUEipVKkcTOCXBVYhvEEwZhX77e4RWJ2LegHta4NW3JZ41a5wzbrEQ_CMuNN0ujhk=@protonmail.com' \
    --to=luis.felipe.la@protonmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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.