[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Intel icc finds too many errors in guile 1.8.8 to compile
From: |
Ludovic Courtès |
Subject: |
Re: Intel icc finds too many errors in guile 1.8.8 to compile |
Date: |
Wed, 07 Oct 2009 00:50:14 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) |
Hi,
Neil Jerram <address@hidden> writes:
> address@hidden (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’.