[#7809] uninit bug in yaml/emitter.c — "Pat Eyler" <rubypate@...>
During our hacking night, we also looked at an UNINIT bug in yaml/emitter.c
[#7813] :!~ not a symbol — noreply@...
Bugs item #4344, was opened at 2006-05-03 17:41
[#7818] (security-related) patch to ALLOC macros to prevent integer overflow bugs — "Dominique Brezinski" <dominique.brezinski@...>
While fixing the integer overflow in rb_ary_fill(), it occurred to me
[#7833] segfault on Proc#call after setting a trace_func — Mauricio Fernandez <mfp@...>
$ cat bug2.rb
[#7843] Possible YAMl bug in 1.8.4 — Damphyr <damphyr@...>
OK, while parsing the td2 data from the ruby-lang website we stumbled on
Its probably a bug. I'm not familiar with the specifics, but Ruby
[#7858] Ruby threads working with native threads — "Francis Cianfrocca" <garbagecat10@...>
I recently wrote a network-event extension for Ruby ("eventmachine" in
[#7865] Strange interactions between Struct and 'pp' — noreply@...
Bugs item #4457, was opened at 2006-05-12 17:13
[#7872] Nonblocking socket-connect — "Francis Cianfrocca" <garbagecat10@...>
All, I needed a nonblocking socket connect for my asynchronous-event
In article <3a94cf510605140559l7baa0205le341dac4f47d424b@mail.gmail.com>,
How about introducing the method Socket#set_nonblocking, or alternatively
Hi,
Well, it's ok then. I'm comfortable adding in the nonblocking
Hi,
How about Socket#nbconnect and Socket#nbaccept?
On 5/15/06, Francis Cianfrocca <garbagecat10@gmail.com> wrote:
In article <1147709691.180288.28647.nullmailer@x31.priv.netlab.jp>,
[#7881] Segfault on x86_64 when built with -O0 in CFLAGS — noreply@...
Bugs item #4491, was opened at 2006-05-16 12:46
[#7882] reproducible bug in DRb on OSX — cremes.devlist@...
I've been tearing my hair out the last few days trying to track down
[#7909] SCRIPT_LINES__ issue when loading a file more than once — Mauricio Fernandez <mfp@...>
SCRIPT_LINES__ is an obscure feature very few people care about, but I happen
On Fri, May 19, 2006 at 06:46:05PM +0900, Mauricio Fernandez wrote:
Hi,
[#7923] Nonblocking accept — "Francis Cianfrocca" <garbagecat10@...>
Thanks to the Matz and colleagues for adding the *_nonblock functions. They
[#7928] set_trace_func: binding has wrong self value for return events — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...>
Moin.
Florian Growrote:
String#nstrip ?
Hi all,
When using the Win32API package, I often have to resort to this idiom to get a
string out of a buffer:
string.split(0.chr).first
The problem is that it's kinda slow. No, I can't use String#rstrip or
String#gsub because often there's other junk at the end of the string that
would prevent those methods from working.
What about adding a String#nstrip (null strip) method that would return a
string up to the first NULL character? Here's a simple implementation:
/* Returns the string up to and excluding the first NULL character */
static VALUE rb_str_nstrip(str){
return rb_str_new2(RSTRING(str)->ptr);
}
This does emit a "cast to pointer from integer of different size" warning
however, so perhaps there's a more appropriate approach. Any, you get the
general idea.
It's also about six times faster according to my benchmarks:
# nullbench.rb
require 'benchmark'
MAX = 100000
STRING = "hello\0\0\0\0"
Benchmark.bm do |x|
require 'benchmark'
MAX = 100000
STRING = "hello\0\0\0\0"
Benchmark.bm do |x|
x.report("String#split"){
MAX.times{ STRING.split("\0").first }
}
# Custom method
x.report("String#nstrip"){
MAX.times{ STRING.nstrip }
}
end
djberge@~/programming/ruby-544>/opt/test/bin/ruby nullbench.rb
user system total real
String#split 3.470000 0.020000 3.490000 ( 3.561128)
String#nstrip 0.550000 0.010000 0.560000 ( 0.587311)
Useful? Or too specialized?
Thanks,
Dan
This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful. If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.