From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Ryde Newsgroups: gmane.lisp.guile.devel Subject: Re: Exposing `scm_i_mem2number ()' Date: Thu, 16 Feb 2006 09:11:02 +1100 Message-ID: <87bqx8p91l.fsf@zip.com.au> References: <87d5holin9.fsf@laas.fr> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1140052357 25574 80.91.229.2 (16 Feb 2006 01:12:37 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Feb 2006 01:12:37 +0000 (UTC) Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Thu Feb 16 02:12:35 2006 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F9XhC-0005g5-U3 for guile-devel@m.gmane.org; Thu, 16 Feb 2006 02:12:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9Xgg-0006iO-64 for guile-devel@m.gmane.org; Wed, 15 Feb 2006 20:12:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F9Ury-00087c-1W for guile-devel@gnu.org; Wed, 15 Feb 2006 17:11:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F9Urt-00083I-Bv for guile-devel@gnu.org; Wed, 15 Feb 2006 17:11:27 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9Urs-00081f-Ch for guile-devel@gnu.org; Wed, 15 Feb 2006 17:11:24 -0500 Original-Received: from [61.8.0.84] (helo=mailout1.pacific.net.au) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9Uwr-0002eM-8I for guile-devel@gnu.org; Wed, 15 Feb 2006 17:16:33 -0500 Original-Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k1FMBL3m002366 for ; Thu, 16 Feb 2006 09:11:21 +1100 Original-Received: from localhost (ppp2223.dyn.pacific.net.au [61.8.34.35]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id k1FMBKM3023177 for ; Thu, 16 Feb 2006 09:11:20 +1100 Original-Received: from gg by localhost with local (Exim 3.36 #1 (Debian)) id 1F9UrZ-0001nX-00; Thu, 16 Feb 2006 09:11:05 +1100 Original-To: guile-devel@gnu.org Mail-Copies-To: never In-Reply-To: <87d5holin9.fsf@laas.fr> (Ludovic =?iso-8859-1?Q?Court=E8s's?= message of "Wed, 15 Feb 2006 16:57:14 +0100") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:5720 Archived-At: ludovic.courtes@laas.fr (Ludovic Court=E8s) 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