unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: proposal: scm_c_public_ref et al
Date: Sun, 06 Mar 2011 22:34:22 +0100	[thread overview]
Message-ID: <m3mxl8aq75.fsf@unquote.localdomain> (raw)
In-Reply-To: <87tyfgw4x4.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Sun, 06 Mar 2011 18:10:47 +0100")

Hello,

On Sun 06 Mar 2011 18:10, Thien-Thi Nguyen <ttn@gnuvola.org> writes:

> () Mark H Weaver <mhw@netris.org>
> () Sun, 06 Mar 2011 11:24:33 -0500
>
>    Maybe utf8 is a better choice?
>
> A module name is a list of symbols, so why not use that from the beginning?

The variants without _c_ did just that, so no problem there.  The
module_name like "ice-9 eval-string" already exists in
scm_c_resolve_module, so I'm not making that bit up.

My interest is to make invoking Scheme code in modules from C easier,
with less fussiness on the C side.  Your ideas are interesting, but
I don't think they are appropriate for the particular problem I am
interested in.

> BTW, i agree that all C strings should be explicitly specified as UTF-8.

ACK.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-03-06 21:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-06 11:24 proposal: scm_c_public_ref et al Andy Wingo
2011-03-06 16:24 ` Mark H Weaver
2011-03-06 17:10   ` Thien-Thi Nguyen
2011-03-06 21:34     ` Andy Wingo [this message]
2011-03-06 21:10   ` Andy Wingo
2011-03-06 22:22 ` Ludovic Courtès
2011-03-07 10:45   ` Andy Wingo

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=m3mxl8aq75.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ttn@gnuvola.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).