From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: Exposing `scm_i_mem2number ()'
Date: Wed, 15 Feb 2006 23:57:12 +0200 [thread overview]
Message-ID: <874q30z3nr.fsf@zagadka.de> (raw)
In-Reply-To: <87d5holin9.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 15 Feb 2006 16:57:14 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> I think it'd be nice to export `scm_i_mem2number ()'. My initial plan
> was to just rename it `scm_c_string_to_number ()' and document it.
>
> However, due to the eventual support for various encodings, we'd rather
> need to have something like `scm_c_locale_string_to_number ()'. The
> problem is: how do we handle the LEN argument for arbitrary encodings?
> Should it be documented as the number of chars (not octets) that compose
> the string?
I'd make it the number of octets, to remain in sync with
scm_from_locale_stringn, etc.
> Suggestions?
But, what about scm_string_to_number (scm_from_locale_string (...))?
Isn't that good enough?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-15 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 15:57 Exposing `scm_i_mem2number ()' Ludovic Courtès
2006-02-15 21:57 ` Marius Vollmer [this message]
2006-02-16 12:17 ` Tomas Zerolo
2006-02-16 13:35 ` Ludovic Courtès
2006-03-08 9:33 ` Ludovic Courtès
2006-03-16 10:07 ` Ludovic Courtès
2006-03-17 0:58 ` Kevin Ryde
2006-03-17 9:01 ` Ludovic Courtès
2006-03-21 0:53 ` Kevin Ryde
2006-02-15 22:11 ` Kevin Ryde
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=874q30z3nr.fsf@zagadka.de \
--to=mvo@zagadka.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).