unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@gnu.org>
Subject: gh_inexact_p error in 1.7.x
Date: Wed, 30 Nov 2005 16:16:22 -0800	[thread overview]
Message-ID: <200511301616.22258.bkorb@gnu.org> (raw)


Hi Rob et al.,

Now for something completely different.  Obviously, I have not yet
updated my code to figure out what sort of thing it is that I got
back from my eval call.  Nevertheless, my understanding was that
you ought to be able to call WHATEVER_p with any bit pattern and
have it say, "Yes, it is" or "No, it is not" without a fail-exit.
Not true in Guile 1.7.2.  Is this fixed?  Thanks!  - Bruce

typ = (SCM) 0x504

 	28	LOCAL teGuileType
 	29	gh_type_e( SCM typ )
-	30	{
-	31	    if (gh_boolean_p(    typ ))   return GH_TYPE_BOOLEAN;
-	32	    if (gh_symbol_p(     typ ))   return GH_TYPE_SYMBOL;
-	33	    if (gh_char_p(       typ ))   return GH_TYPE_CHAR;
-	34	    if (gh_vector_p(     typ ))   return GH_TYPE_VECTOR;
-	35	    if (gh_pair_p(       typ ))   return GH_TYPE_PAIR;
-	36	    if (gh_number_p(     typ ))   return GH_TYPE_NUMBER;
-	37	    if (AG_SCM_STRING_P( typ ))   return GH_TYPE_STRING;
-	38	    if (gh_procedure_p(  typ ))   return GH_TYPE_PROCEDURE;
-	39	    if (gh_list_p(       typ ))   return GH_TYPE_LIST;
-	40	    if (gh_inexact_p(    typ ))   return GH_TYPE_INEXACT;  <<=== throws error
-	41	    if (gh_exact_p(      typ ))   return GH_TYPE_EXACT;
 	42	
-	43	    return GH_TYPE_UNDEFINED;
-	44	}


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


             reply	other threads:[~2005-12-01  0:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01  0:16 Bruce Korb [this message]
2005-12-01  0:44 ` gh_inexact_p error in 1.7.x Kevin Ryde
2005-12-05  4:08   ` No way out Bruce Korb
2005-12-05  4:35     ` Bruce Korb
2005-12-07  1:31       ` Marius Vollmer
2005-12-05 22:20     ` Kevin Ryde
2005-12-06 10:58       ` Han-Wen Nienhuys
2005-12-28 15:59         ` Neil Jerram
2005-12-31 15:09           ` Han-Wen Nienhuys
2005-12-31 15:14             ` Neil Jerram
2006-01-01 19:58               ` Han-Wen Nienhuys
2006-01-02 15:42                 ` Neil Jerram
2006-01-02 18:54                   ` Neil Jerram
2006-01-04 21:13                     ` Backtrace and enhanced catch Neil Jerram
2006-01-14 12:41                       ` Neil Jerram
2006-01-22 13:47                         ` Marius Vollmer
2006-01-23 20:11                           ` Neil Jerram
2006-01-24 21:34                             ` Marius Vollmer
2006-01-16  8:38                       ` Ludovic Courtès
2006-01-18 23:08                         ` Neil Jerram
2006-01-19  9:38                           ` Ludovic Courtès
2006-01-21 11:26                             ` Neil Jerram
2006-01-26 23:29                       ` Kevin Ryde
2006-01-27 19:30                         ` Neil Jerram
2006-01-31 20:07                           ` Kevin Ryde
2006-02-01 23:04                             ` Neil Jerram
2006-02-04  0:46                               ` Kevin Ryde
2006-02-04 15:41                                 ` Neil Jerram
2005-12-07  1:07     ` No way out Marius Vollmer
2005-12-07  1:55       ` Rob Browning
2005-12-13 20:32         ` Marius Vollmer
2005-12-28 16: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=200511301616.22258.bkorb@gnu.org \
    --to=bkorb@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).