From: Pierpaolo Bernardi <olopierpa@gmail.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: scheme problem!
Date: Thu, 12 May 2011 13:34:04 +0200 [thread overview]
Message-ID: <BANLkTinciw6n1mwXpCqo0sOrKbo_BZR-PA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik+FgZQ1T2quSLGB00gHaJM6aw84Q@mail.gmail.com>
On Thu, May 12, 2011 at 12:59, Stefan Israelsson Tampe
<stefan.itampe@gmail.com> wrote:
> Somewhere in the program I have,
>
> (pk x)
> (pk (caar l))
> (pk (equal? x (caar l)))
>
> It outputs
>
> ;;; (number)
>
> ;;; (number)
>
> ;;; (#f)
>
>
>
> #f ???? is there more to this then meets the eye?
You will get more significative replies if you post a snippet of code
which allows people to reproduce what you observe without having to
guess what could possibly be causing this.
P.
next prev parent reply other threads:[~2011-05-12 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 10:59 scheme problem! Stefan Israelsson Tampe
2011-05-12 11:34 ` Pierpaolo Bernardi [this message]
2011-05-12 22:02 ` Neil Jerram
2011-05-12 22:23 ` Stefan Israelsson Tampe
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=BANLkTinciw6n1mwXpCqo0sOrKbo_BZR-PA@mail.gmail.com \
--to=olopierpa@gmail.com \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.com \
/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).