unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: bornlibra23 <awarikoo@nse.co.in>
Cc: Guile-devel@gnu.org
Subject: Re: Porting GNU Projects - Guile
Date: Thu, 30 Jul 2009 20:54:09 +0100	[thread overview]
Message-ID: <87skgex7z2.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <24731881.post@talk.nabble.com> (bornlibra's message of "Wed\, 29 Jul 2009 21\:10\:02 -0700 \(PDT\)")

bornlibra23 <awarikoo@nse.co.in> writes:

> Thanks Mike for the heads up but the problem I think is with the source code
> itself. I get the same error on linux though it doesnt die there. I
> preprocessed the code & changed the line like so :
>>From (((((ch) == ' ' | (ch) == '\t') to (((((ch) == ' ' || (ch) == '\t')
> (note the or operator) & the problem went away but then I had the mentioned
> problem. I will build it again & get back to you. My build log seems to be
> dated.

FWIW this is fixed in Guile's master branch:

#ifdef HAVE_ISBLANK
# define CSET_BLANK_PRED(c)  (isblank (c))
#else
# define CSET_BLANK_PRED(c)			\
   (((c) == ' ') || ((c) == '\t'))
#endif

I guess it was missed for a long time because it is rare to have an OS
that doesn't provide isblank().

Regards,
        Neil




  reply	other threads:[~2009-07-30 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-29 15:14 Porting GNU Projects - Guile bornlibra23
2009-07-29 19:25 ` Mike Gran
2009-07-30  4:10   ` bornlibra23
2009-07-30 19:54     ` Neil Jerram [this message]
     [not found]       ` <24969386.post@talk.nabble.com>
2009-08-14 21:29         ` Neil Jerram
2009-08-17  3:57           ` bornlibra23

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=87skgex7z2.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=Guile-devel@gnu.org \
    --cc=awarikoo@nse.co.in \
    /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).