unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: kevin.brott@providence.org, Guile-User <guile-user@gnu.org>
Subject: Re: Guile 1.8.2 Compile Error [GAH]
Date: Wed, 14 Nov 2007 11:17:43 -0800 (PST)	[thread overview]
Message-ID: <107476.82904.qm@web37904.mail.mud.yahoo.com> (raw)

> From: Kevin Brott <kevin.brott@providence.org>

> I find that this line in numbers.c
> 
> 6081: return scm_from_complex_double (cexp (SCM_COMPLEX_VALUE (z)));
> 
> expands to this:
> 
>       return scm_from_complex_double (cexp (((((scm_t_complex *)
> ((((scm_t_bits) (0? (*(SCM*)0=((((SCM *)((scm_t_cell *) (((scm_t_bits)
> (0? (*(SCM*)0=((((z))))): (((z)))))))) [((1))]))):
> (((SCM
> 
 *)((scm_t_cell
> *) (((scm_t_bits) (0? (*(SCM*)0=((((z))))): (((z))))))))
> [((1))]))))))->real) + __I * (((scm_t_complex *) ((((scm_t_bits) (0?
> (*(SCM*)0=((((SCM *)((scm_t_cell *) (((scm_t_bits) (0?
> (*(SCM*)0=((((z))))): (((z)))))))) [((1))]))): (((SCM *)((scm_t_cell *)
> (((scm_t_bits) (0? (*(SCM*)0=((((z))))): (((z))))))))
> [((1))]))))))->imag))));
> 

You are correct. There is a value in that macro called "_Complex_I" that is, for some reason, being processed down to "__I", losing the word "Complex".

What if you replace "_Complex_I" with "(0.0 + 1.0i)" ?

Good Luck,

Mike Gran

----- Original Message ----
> From: Kevin Brott <kevin.brott@providence.org>
> To: Guile-User <guile-user@gnu.org>
> Sent: Wednesday, November 14, 2007 10:37:01 AM
> Subject: Re: Guile 1.8.2 Compile Error [GAH]
> 
> 
> On Wed, 2007-11-14 at 09:59 -0800, Kevin Brott wrote:
> 
> > No - it bombs out now, trying to compile numbers.c  with this error:
> > 
> > numbers.c: In function 'scm_exp':
> > numbers.c:6081: error: '__I' undeclared (first use in this function)
> > numbers.c:6081: error: (Each undeclared identifier is reported
> only
> 
 once
> > numbers.c:6081: error: for each function it appears in.)
> > 
> > And I'm trying to work out where that __I is hiding.
> > 
> 
> Found where it's manifesting, now to figure out why ... from the
> guile-1.8.3 directory, if I do:
> 
>   cpp -I. -DHAVE_CONFIG_H libguile/numbers.c -o foo.cpp
> 
> I find that this line in numbers.c
> 
> 6081: return scm_from_complex_double (cexp (SCM_COMPLEX_VALUE (z)));
> 
> expands to this:
> 
>       return scm_from_complex_double (cexp (((((scm_t_complex *)
> ((((scm_t_bits) (0? (*(SCM*)0=((((SCM *)((scm_t_cell *) (((scm_t_bits)
> (0? (*(SCM*)0=((((z))))): (((z)))))))) [((1))]))):
> (((SCM
> 
 *)((scm_t_cell
> *) (((scm_t_bits) (0? (*(SCM*)0=((((z))))): (((z))))))))
> [((1))]))))))->real) + __I * (((scm_t_complex *) ((((scm_t_bits) (0?
> (*(SCM*)0=((((SCM *)((scm_t_cell *) (((scm_t_bits) (0?
> (*(SCM*)0=((((z))))): (((z)))))))) [((1))]))): (((SCM *)((scm_t_cell *)
> (((scm_t_bits) (0? (*(SCM*)0=((((z))))): (((z))))))))
> [((1))]))))))->imag))));
> 
> So hunting back to where SCM_COMPLEX_VALUE is defined in numbers.c, we
> get
>     168 #define SCM_COMPLEX_VALUE(z) \
>     169   (SCM_COMPLEX_REAL (z) + _Complex_I * SCM_COMPLEX_IMAG (z))
> 
> So it looks like _Complex_I is rendering as __I - and that prpbably
> isn't correct.
> 
> -- 
> #include 
> /* Kevin Brott  
>  * Unix Systems Engineer - SA Group - Provtech
>  * Providence Health Systems, Tigard, OR
>  */
> 
> 
> DISCLAIMER:
> This message is intended for the sole use of the addressee, and
> may
> 
 contain information that is privileged, confidential and exempt
> from
> 
 disclosure under applicable law. If you are not the addressee you are
> hereby
> 
 notified that you may not use, copy, disclose, or distribute to
> anyone
> 
 the message or any information contained in the message. If you
> have
> 
 received this message in error, please immediately advise the sender
> by
> 
 reply email and delete this message.
> 
> 
> _______________________________________________
> Guile-user mailing list
> Guile-user@gnu.org
> http://lists.gnu.org/mailman/listinfo/guile-user
> 




_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


             reply	other threads:[~2007-11-14 19:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 19:17 Mike Gran [this message]
2007-11-14 20:28 ` Guile 1.8.2 Compile Error [GAH] Kevin Brott
2007-11-15 12:59 ` Ludovic Courtès
2007-11-15 18:10   ` Kevin Brott
2007-11-15 20:18     ` Kevin Brott
  -- strict thread matches above, loose matches on Subject: below --
2007-11-14  1:00 Mike Gran
     [not found] <1194888764.4167.13.camel@vanguard.or.providence.org>
     [not found] ` <87fxzbql1e.fsf@chbouib.org>
2007-11-12 21:37   ` Guile 1.8.2 Compile Error Kevin Brott
2007-11-12 23:14     ` Ludovic Courtès
2007-11-12 23:39       ` Guile 1.8.2 Compile Error [GAH] Kevin Brott
2007-11-12 23:46         ` Kevin Brott
2007-11-12 23:51         ` Ludovic Courtès
2007-11-13  0:08           ` Kevin Brott
2007-11-13 19:00             ` Kevin Brott
2007-11-13 22:20               ` Ludovic Courtès
2007-11-13 23:05                 ` Kevin Brott
2007-11-14  0:39                   ` Neil Jerram
2007-11-14  1:29                     ` Kevin Brott
2007-11-14  1:54                       ` Kevin Brott
2007-11-14 13:35                     ` Ludovic Courtès
2007-11-14 17:59                       ` Kevin Brott
2007-11-14 18:37                         ` Kevin Brott
2007-11-15 20:50                       ` Neil Jerram
2007-11-16 16:50                         ` Ludovic Courtès
2007-11-26 21:26                           ` 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=107476.82904.qm@web37904.mail.mud.yahoo.com \
    --to=spk121@yahoo.com \
    --cc=guile-user@gnu.org \
    --cc=kevin.brott@providence.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).