unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: Intel icc finds too many errors in guile 1.8.8 to compile
Date: Wed, 07 Oct 2009 00:50:14 +0200	[thread overview]
Message-ID: <873a5wuogp.fsf@gnu.org> (raw)
In-Reply-To: 87ab04qlka.fsf@ossau.uklinux.net

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> ludo@gnu.org (Ludovic Courtès) writes:

[...]

>> So these could become, say:
>>
>>   enum scm_dynwind_flags
>>   {
>>     SCM_F_DYNWIND_NOT_REWINDABLE = 0,
>>     SCM_F_DYNWIND_NOT_REWINDABLE
>>   };
>>
>>   typedef enum scm_dynwind_flags scm_t_dynwind_flags;
>>
>>   enum scm_wind_flags
>>   {
>>     SCM_F_WIND_NON_LOCAL_EXIT = 0,
>>     SCM_F_WIND_EXPLICITLY
>>   };
>>
>>   typedef enum scm_wind_flags scm_t_wind_flags;
>
> But wouldn't this approach break as soon as we added another flag, in
> the way that I described in my previous email?

Yes it would.

But the underlying question is: is the set of flags likely to change?
If the answer is “no” (which I think it is), it’s probably safe to go
for an ‘enum’, as these flags cannot be combined anyway.

Thanks,
Ludo’.





  reply	other threads:[~2009-10-06 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  9:22 Intel icc finds too many errors in guile 1.8.8 to compile I.Gutheil
2009-10-02 21:21 ` Neil Jerram
2009-10-03  9:43   ` Ludovic Courtès
     [not found]     ` <8763avzfh9.fsf@ossau.uklinux.net>
     [not found]       ` <87r5tjbb0h.fsf@gnu.org>
2009-10-06 21:06         ` Neil Jerram
2009-10-06 22:50           ` Ludovic Courtès [this message]
2009-10-07 21:09             ` Neil Jerram

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=873a5wuogp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guile@gnu.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).