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: Sat, 03 Oct 2009 11:43:05 +0200	[thread overview]
Message-ID: <878wfsu82e.fsf@gnu.org> (raw)
In-Reply-To: 87my49bifn.fsf@ossau.uklinux.net

Hi,

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

> "I.Gutheil" <i.gutheil@fz-juelich.de> writes:

[...]

>> debug.c(62): error #188: enumerated type mixed with another type
>>     scm_dynwind_begin (0);
>>
>> This could be "corrected" by declaring
>> in dynwind.h
>> SCM_API void scm_dynwind_begin (int) instead of the derived datatype
>> which could only be 1
>> and in dynwind.c
>>
>> void
>> scm_dynwind_begin (int flags)
>> ...
>
> Agreed; using enums here is just asking for trouble.  I've changed it to
> #defines.

Per C99 Section 6.4.4.3, “an identifier declared as an enumeration
constant has type int”, so ICC is pedantic.

I think having disjoint ‘scm_t_wind_flags’ and ‘scm_t_dynwind_flags’
types was helpful to indicate which flags are valid for which function.
Thus, I’d rather have fixed it by adding a named enumeration constant
for 0 in each of these types.

At any rate, I think we should probably keep “typedef int
scm_t_wind_flags;” and “typedef int scm_t_dynwind_flags”.

What do you think?

Thanks,
Ludo’.





  reply	other threads:[~2009-10-03  9:43 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 [this message]
     [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
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=878wfsu82e.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).