unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Jean Abou Samra <jean@abou-samra.fr>
To: Joshua Branson <jbranso@dismail.de>
Cc: 59221@debbugs.gnu.org
Subject: bug#59221: (file-exists? #f) raises an exception
Date: Sat, 12 Nov 2022 18:57:20 +0100	[thread overview]
Message-ID: <1D1C3D58-0BC7-40C2-AC1A-38E59C53FE00@abou-samra.fr> (raw)
In-Reply-To: <87y1sghxm2.fsf@dismail.de>



> Le 12 nov. 2022 à 18:50, Joshua Branson via Bug reports for GUILE, GNU's Ubiquitous Extension Language <bug-guile@gnu.org> a écrit :
> 
> 
> Hello you lovely guile people!
> 
> This bug is so simple the subject line says it all!
> 
> file-exists? is a predicate, but
> 
> #+BEGIN_SRC scheme
> (file-exists? #f)
> ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> In procedure stat: Wrong type argument in position 1 (expecting open file port): #f
> 
> Entering a new prompt.  Type `,bt' for a backtrace or `,q' to continue.
> #+END_SRC
> 
> I will shortly tag this as "easy".  Can you lovely maintainers give me
> about a week to try to fix this myself?
> 
> Thanks,
> 
> Joshua
> avid fantany reader


What’s the problem here?

It is normal for predicates to be defined only on certain types. You will find the same with positive?, string-null? and the like.

Regards,
Jean








  reply	other threads:[~2022-11-12 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 17:49 bug#59221: (file-exists? #f) raises an exception Joshua Branson via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2022-11-12 17:57 ` Jean Abou Samra [this message]
2022-11-13  2:15 ` jbranso--- via Bug reports for GUILE, GNU's Ubiquitous Extension Language
2022-11-13  6:44   ` tomas
2022-11-13 10:34     ` Jean Abou Samra
2022-11-16 15:27       ` Joshua Branson via Bug reports for GUILE, GNU's Ubiquitous Extension Language

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=1D1C3D58-0BC7-40C2-AC1A-38E59C53FE00@abou-samra.fr \
    --to=jean@abou-samra.fr \
    --cc=59221@debbugs.gnu.org \
    --cc=jbranso@dismail.de \
    /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).