ruby-changes:5639
From: usa <ko1@a...>
Date: Fri, 13 Jun 2008 14:57:11 +0900 (JST)
Subject: [ruby-changes:5639] Ruby:r17146 (trunk): * README.EXT: ditto.
usa 2008-06-13 14:56:51 +0900 (Fri, 13 Jun 2008)
New Revision: 17146
Modified files:
trunk/ChangeLog
trunk/README.EXT
Log:
* README.EXT: ditto.
http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/ChangeLog?r1=17146&r2=17145&diff_format=u
http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/trunk/README.EXT?r1=17146&r2=17145&diff_format=u
Index: README.EXT
===================================================================
--- README.EXT (revision 17145)
+++ README.EXT (revision 17146)
@@ -31,7 +31,7 @@
T_STRING string
T_REGEXP regular expression
T_ARRAY array
- T_FIXNUM Fixnum(31bit integer)
+ T_FIXNUM Fixnum(31bit or 63bit integer)
T_HASH associative array
T_STRUCT (Ruby) structure
T_BIGNUM multi precision integer
@@ -106,6 +106,13 @@
is a String. Notice that the macros take only the lvalue as their
argument, to change the value of var in place.
+You can also use the macro named StringValueCStr(). This is just
+like StringValuePtr(), but always add nul character at the end of
+the result. If the result contains nul character, this macro causes
+the ArgumentError exception.
+StringValuePtr() doesn't gurantee to exist nul at the end of the
+result, and the result may contain nul.
+
In version 1.6 or earlier, STR2CSTR() was used to do the same thing
but now it is deprecated in version 1.7, because STR2CSTR() has a risk
of a dangling pointer problem in the to_str() implicit conversion.
Index: ChangeLog
===================================================================
--- ChangeLog (revision 17145)
+++ ChangeLog (revision 17146)
@@ -5,6 +5,8 @@
* README.EXT.ja: describe about StringValueCStr().
+ * README.EXT: ditto.
+
Fri Jun 13 14:24:37 2008 Nobuyoshi Nakada <nobu@r...>
* gc.c (rb_memerror): exit with EXIT_FAILURE instead of magic number.
--
ML: ruby-changes@q...
Info: http://www.atdot.net/~ko1/quickml/