unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Exposing `scm_i_mem2number ()'
Date: Thu, 16 Feb 2006 09:11:02 +1100	[thread overview]
Message-ID: <87bqx8p91l.fsf@zip.com.au> (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:
>
> However, due to the eventual support for various encodings, we'd rather
> need to have something like `scm_c_locale_string_to_number ()'.

That could be more relaxed than specifically the "locale" encoding.
If all valid numbers are ascii then it doesn't matter what the
extended characters are, they're all invalid.  (For ascii-compatible
encodings, of course.)  Maybe scm_c_ascii_string_to_number.

> Should it be documented as the number of chars (not octets) that compose
> the string?

I think bytes is usual.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      parent reply	other threads:[~2006-02-15 22:11 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
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 [this message]

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=87bqx8p91l.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).