unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Viktor Pavlenko <vvp@rogers.com>
Cc: guile-user@gnu.org
Subject: Re: SCM to C string
Date: Thu, 20 Jun 2002 18:10:15 -0400	[thread overview]
Message-ID: <15634.21191.16739.686077@mriya.ua> (raw)
In-Reply-To: <15634.17248.994413.539036@minos.phy.bnl.gov>

>>>>> "BV" == Brett Viren <bv@bnl.gov> writes:

    BV> Viktor Pavlenko writes:
    >> 
    >> For instance I'd like convert SCM object which contains '("a"
    >> 1) into C string "(\"a\" 1)".

    BV> Why do you need to escape the double quotes?  If you have a
    BV> null terminated string, you should be able to print it (or
    BV> pass it to a Gui or whatever) in C just fine.  Or do I miss
    BV> something.

You don't miss anything. I escaped the quotes to be able to show the
whole string in quotes.

    BV> I asked a similar question some time back, maybe the following
    BV> can help.  It turns a scheme procedure into its coresponding
    BV> source code.  But, I guess it will fail to do what you want
    BV> for compiled procedures as well as arbitrary scheme forms.
    BV> The following is C++, if you are using strict C just return
    BV> the "cptr" and ignore the "string" object.

I use C++. Thanks a lot!

Viktor

    BV> [code]


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


  reply	other threads:[~2002-06-20 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 20:39 SCM to C string Viktor Pavlenko
2002-06-20 21:04 ` Brett Viren
2002-06-20 22:10   ` Viktor Pavlenko [this message]
2002-06-20 22:04 ` Christopher Cramer
2002-06-20 22:09   ` Viktor Pavlenko
2002-06-21  4:17     ` Viktor Pavlenko
2002-06-21 15:22       ` Rob Browning

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=15634.21191.16739.686077@mriya.ua \
    --to=vvp@rogers.com \
    --cc=guile-user@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).