http://blog.gmane.org/gmane.comp.lang.ruby.core hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.lang.ruby.core/19499 Bug #804: Ruby 1.9.1 preview 2 : make test failure http://redmine.ruby-lang.org/issues/show/804 Author: Philippe Lucas Status: Open, Priority: Normal Version built on Fedora core 2 x686 with gcc 4.0.2 in a sub directory (UNIX) of the main ruby source with ./configure --prefix=/h/phil/DEV/RUBY/ruby-191pv2 --enable-shared --enable-install-doc --enable-pthread --with-mantype=man ./ruby -v => ruby 1.9.1 (2008-12-01 revision 20438) [i686-linux] Note that : ruby -v => ruby 1.8.7 (2008-05-31 patchlevel 0) [i686-linux] In the announce message of this release, i read : == Improvements * You can "make test" without installing ruby. So make test gives this error : test_flip.rb /h/phil/DEV/RUBY/ruby-1.9.1-preview2/UNIX/ruby: error while loading shared libraries: libruby.so.1.9: cannot open shared object file: No such file or directory which is not very suprising !. Regards. ---------------------------------------- http://redmine.ruby-lang.org Philippe Lucas 2008-12-01T15:44:35 http://comments.gmane.org/gmane.comp.lang.ruby.core/19498 Ruby 1.9.1 Preview 2 has been released. This is a preview release of Ruby 1.9, which will be the first stable version of Ruby 1.9 series. If you encounter a bug or a problem, please let us know it via the official issue tracking system (http://redmine.ruby-lang.org ). == Location * ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.1-preview2.tar.bz2 SIZE: 6148131 bytes MD5: 62126475998ede5318c1bc82c40d5f48 SHA256: 2c419dc325c6a75fb7b961496c0dd54f2729e6e01730589c4fb06e34ddd7a7cc * ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.1-preview2.tar.gz SIZE: 7375483 bytes MD5: 7699b9e54c53b16640d40a213588e704 SHA256: dd737d26212d68c26ecb4d6e2ed180a0d7d5e27fb7bd2c819935494daa1cf50b * ftp://ftp.ruby-lang.org/pub/ruby/1.9/ruby-1.9.1-preview2.zip SIZE: 8612618 bytes MD5: d3ae200280b75801bfc5c090d3592577 SHA256: 96b6a2745b64f03ffbd5da97f93a2676365e3900cb8f6bf820f47739ef8d3fa9 == Improvements * supports 21 new character encodings. * works better with RubyGems. * handles SEGV better when sys Yugui (Yuki Sonoda 2008-12-01T13:25:50 http://comments.gmane.org/gmane.comp.lang.ruby.core/19487 Hi, Windows Vista (Home Premium) MS VC++ 9 (cl 15) Ruby 1.8.6-p114 and Ruby 1.8.6-p237 eval.c ... eval.c(9839) : fatal error C1189: #error : unsupported platform NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\BIN\amd64\cl.EXE"' : return code '0x2 ' Stop. Where the relevant code is: #if !defined SAVE_WIN32_EXCEPTION_LIST && !defined _WIN32_WCE # error unsupported platform #endif #endif Regards, Dan Daniel Berger 2008-11-30T13:42:36 http://comments.gmane.org/gmane.comp.lang.ruby.core/19472 I noticed that the following reg exp causes syntax error in 1.9.1 (I use tip of the branch): /\n(\.\/)?(.*spec\.rb):[\d]+:\Z?/ To reproduce, just fire up irb of 1.9.1 and try to assign this literal to some variable. The problem is with ? quantifier following \Z. I could not find any information about this restriction on the web and have no Mastering regular expressions book at hand. Could someone shed some light on whether it is 1.9.1 engine restriction, general regular expressions restriction or possible 1.9.1 bug? Just in case: this regexp comes from autospec in RSpec. Thank you, MK Michael Klishin 2008-11-28T23:14:36 http://comments.gmane.org/gmane.comp.lang.ruby.core/19469 Bug #800: Problem with Array class http://redmine.ruby-lang.org/issues/show/800 Author: Francois Proulx Status: Open, Priority: High If you test this simple program, you will see why array should be dup on assignment ... a=1 b=1 c=[a,b] def foo(x) x[0] +=1 x[1] +=1 end d = c e = d f = e foo(f) p c[0],c[1] ---------------------------------------- http://redmine.ruby-lang.org Francois Proulx 2008-11-28T20:34:20 http://comments.gmane.org/gmane.comp.lang.ruby.core/19442 Bug #799: cross compile 1.9.1-preview1 is not possible http://redmine.ruby-lang.org/issues/show/799 Author: Luis Lavena Status: Open, Priority: Normal Target version: 1.9.1 Hello everybody. I tried to cross compile 1.9.1-preview1 under ubuntu. It succeeded with 1.8.6-p287 and p114 but failed with 1.9. Used the following compile flags: <pre><code>--host=i586-mingw32msvc --target=i386-mingw32 --build=i686-linux --enable-shared</code></pre> This is the snipped of the output <pre><code>make[1]: Leaving directory `/home/luislavena/sources/cross-ruby/builds/ruby-1.9.1-preview1' make -f enc.mk RUBY="ruby -I/home/luislavena/sources/cross-ruby/builds/ruby-1.9.1-preview1 -rfake " MINIRUBY="ruby -I/home/luislavena/sources/cross-ruby/builds/ruby-1.9.1-preview1 -rfake " encs make[1]: Entering directory `/home/luislavena/sources/cross-ruby/builds/ruby-1.9.1-preview1' mkdir -p .ext/i386-mingw32/enc .ext/i386-mingw32/enc/trans enc enc/trans make[1]: Leaving directory `/home/luislavena/sources/cross-ruby/builds/ruby-1 Luis Lavena 2008-11-26T21:57:39 http://comments.gmane.org/gmane.comp.lang.ruby.core/19440 I'm probably missing something trivial, but given the following Ruby code: class Myclass < at >< at >myvar = 1 def self.myvar return < at >< at >myvar end end I can access < at >< at >myvar from Ruby with Myclass::myvar. Great, but now I need to access that same variable through a C extension. I think I can get it by doing: VALUE myvar = rb_eval_string("Myclass::myvar"); but surely there's a better way? I'm thinking something like rb_cvar_get() but that requires that I pass in a VALUE and all I have is a string at this point, "Myclass". Christopher Thompson 2008-11-26T19:49:32 http://comments.gmane.org/gmane.comp.lang.ruby.core/19436 Hello ruby-core, Today I was playing around with manipulating strings containing binary data, i.e. "\xaa\xab\xac\xad\xae" and using the new String methods available in Ruby 1.9. The exercise I was trying out was to extract out a range of bytes as Fixnums. Kind of like String#bytes but I was only interested in a subarray. Like so: "\xaa\xab\xac\xad\xae".bytes.to_a[1,3] # => [171, 172, 173] This works but operates on the entire data set which I imagine is fairly expensive... So I chopped it up before hand like so: "\xaa\xab\xac\xad\xae"[1,3].bytes.to_a => [171, 172, 173] Much better. This works fine when using the ASCII-8BIT encoding. As soon as you use something like UTF-8 it fails because the [] method now works on characters instead of bytes. data = "\xc3\xa9\xc3\xa9" # => "\xC3\xA9\xC3\xA9" data.force_encoding("utf-8") # => "" data[0,2].bytes.to_a # => [195, 169, 195, 169] Here I get four bytes instead of the first two which I wanted. data.bytes.to_a[0,2] # => [195, 169] So having said that I mu Emiel van de Laar 2008-11-26T16:07:08 http://comments.gmane.org/gmane.comp.lang.ruby.core/19430 I've copied code from main.c in an attempt to embed the ruby interpreter in a very simple program, but I'm getting an error: [pbrannan< at >zem emb]$ cat emb.c #include <ruby.h> int main(int argc, char * argv[]) { ruby_sysinit(&argc, &argv); RUBY_INIT_STACK; ruby_init(); void * node = ruby_options(argc, argv); ruby_run_node(node); } [pbrannan< at >zem emb]$ gcc \ -I/usr/local/include/ruby1.9-1.9.0 \ -I/usr/local/include/ruby1.9-1.9.0/i686-linux \ -I/usr/local/include/ruby1.9-1.9.0 \ -I/usr/local/include/ruby1.9-1.9.0/i686-linux \ emb.c -o emb \ -lpthread -lrt -ldl -lcrypt -lm \ -lc -Wl,-R -Wl,/usr/local/lib \ -L/usr/local/lib -lruby1.9-static [pbrannan< at >zem emb]$ ./emb ./emb: error while loading shared libraries: /usr/local/lib/ruby1.9/1.9.0/i686-linux/enc/encdb.so: undefined symbol: rb_encdb_declare [pbrannan< at >zem emb]$ nm emb | grep rb_encdb_declare 08104730 T rb_encdb_declare [pbrannan< at >zem emb]$ nm `which ruby1.9` | grep rb_encdb_declare 08112110 T rb_encdb_declare Any idea where I'm going wrong? Paul Paul Brannan 2008-11-26T14:30:55 http://comments.gmane.org/gmane.comp.lang.ruby.core/19424 Bug #798: r19320 updated REXML but didn't increment REXML::VERSION http://redmine.ruby-lang.org/issues/show/798 Author: Jeremy Kemper Status: Open, Priority: Normal r19320 backported the entity_expansion_limit fix to 1.8, but REXML::VERSION was not incremented from "3.1.7.2" to "3.1.7.3" # Must load REXML to check for DoS safety require 'rexml/document'; REXML::Document.respond_to?(:entity_expansion_limit=). # Simpler and saves 1MB memory. require 'rexml/rexml'; REXML::VERSION > '3.1.7.2' Index: lib/rexml/rexml.rb =================================================================== --- lib/rexml/rexml.rb(revision 20354) +++ lib/rexml/rexml.rb(working copy) < at >< at > -23,7 +23,7 < at >< at > # online[http://www.germane-software.com/software/rexml/docs/tutorial.html] module REXML COPYRIGHT = "Copyright \xC2\xA9 2001-2006 Sean Russell <ser< at >germane-software.com>" - VERSION = "3.1.7.2" + VERSION = "3.1.7.3" DATE = "2007/275" REVISION = "$Revision$".gsub(/\$Revision:|\$/,'').strip ----------------------------- Jeremy Kemper 2008-11-26T08:47:51 http://comments.gmane.org/gmane.comp.lang.ruby.core/19403 Bug #797: bug or feature: local method ? http://redmine.ruby-lang.org/issues/show/797 Author: Francois Proulx Status: Open, Priority: Normal It's possible to create a method inside a method. I've never see any mention of this in any documentation. It's a feature that is officially part the spec of the language or it's a bug ? ---------------------------------------- http://redmine.ruby-lang.org Francois Proulx 2008-11-25T18:20:35 http://comments.gmane.org/gmane.comp.lang.ruby.core/19402 Bug #796: dynamic constant assignment http://redmine.ruby-lang.org/issues/show/796 Author: Francois Proulx Status: Open, Priority: Normal I understand the difference in the use of variable and constant. But sometime you need to be able to assigned a value dynamiquely when you are initializing your application. I see 2 possibility to address the problem: - a interpreter's directive (which would demand a major change of the interpreter) - a method to allow specificely a dynamic assignment ---------------------------------------- http://redmine.ruby-lang.org Francois Proulx 2008-11-25T18:05:12 http://comments.gmane.org/gmane.comp.lang.ruby.core/19399 Bug #791: Fiber using a Proc object with a parameter having default value doesn't work http://redmine.ruby-lang.org/issues/show/791 Author: Florian Gilcher Status: Open, Priority: Normal Category: core If you pass a Proc with a default value on a parameter into a Fiber, the default value is ignored. Example by Wolfgang Nádasi-Donner: irb(main):001:0> p = ->(i=4){i+5} => #<Proc:0xe8a370< at >(irb):1 (lambda)> irb(main):002:0> p[] => 9 irb(main):003:0> Fiber.new(&p).resume NoMethodError: undefined method `+' for nil:NilClass from (irb):1:in `block (3 levels) in irb_binding' A more useful example is... irb(main):001:0> f = Fiber.new(&(->(i=5){loop{Fiber.yield i+=1}})) => #<Fiber:0xe860f8> irb(main):002:0> f.resume NoMethodError: undefined method `+' for nil:NilClass from (irb):1:in `block (4 levels) in irb_binding' from (irb):1:in `loop' from (irb):1:in `block (3 levels) in irb_binding' Regards, Florian Gilcher ---------------------------------------- http://redmine.rub Florian Gilcher 2008-11-25T09:28:32 http://comments.gmane.org/gmane.comp.lang.ruby.core/19397 Bug #790: Unexpected Behaviour: Fibers as superclass don http://redmine.ruby-lang.org/issues/show/790 Author: Florian Gilcher Status: Open, Priority: Normal Category: core This is possibly just undocumented and intended behaviour: ---------------------------------------- http://redmine.ruby-lang.org Florian Gilcher 2008-11-25T09:22:53 http://comments.gmane.org/gmane.comp.lang.ruby.core/19393 Bug #788: r20287 broke rb_str_replace http://redmine.ruby-lang.org/issues/show/788 Author: Jeremy Kemper Status: Open, Priority: High Assigned to: Nobuyoshi Nakada $ ruby -rrexml/document -e "REXML::Document.new('<a>b</a>')" ruby(17210) malloc: *** error for object 0xab1f8: pointer being reallocated was not allocated *** set a breakpoint in malloc_error_break to debug ruby(17210) malloc: *** error for object 0xab1f8: pointer being reallocated was not allocated *** set a breakpoint in malloc_error_break to debug /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/text.rb:77:in `initialize_copy': failed to allocate memory (NoMemoryError) from /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/text.rb:77:in `clone' from /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/text.rb:77:in `initialize' from /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/parsers/treeparser.rb:43:in `new' from /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/parsers/treeparser.rb:43:in `parse' from /usr/local/ruby/1.8.7-gc/lib/ruby/1.8/rexml/document.rb:227: Jeremy Kemper 2008-11-25T03:35:18 http://comments.gmane.org/gmane.comp.lang.ruby.core/19390 Hi! I am a little bit surprized to get no (=0) answer for my questions in No. 20015 and No. 20025, and no comment to No. 20071 from Florian Gilcher, because the basic questions should be easy to be answered, and an answer will us enable for further testing (=playing to explore the feasibilities). The questions simly were: Are the effects features or bugs? Wolfgang Nádasi-Donner Wolfgang Nádasi-Donner 2008-11-24T22:06:58 http://comments.gmane.org/gmane.comp.lang.ruby.core/19384 Is test/unit gone for good from Ruby 1.9? Is it all going to be miniunit now? http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/branches/ruby_1_9_1/lib/test/unit.rb?revision=19969&view=markup James Edward Gray II James Gray 2008-11-24T14:48:02 http://comments.gmane.org/gmane.comp.lang.ruby.core/19382 Hi, as some of you might have noticed, Wolfgang Nádasi-Donner and I had a look into the new Fiber feature of Ruby 1.9. Aside from the bugs[1] it is also evident that the documentation for Fibers is severely lacking (as in: non-existant). We have a hard time finding actual documentation and reasons for most things concerning Fibers. That leads to the general question: Should missing, incomplete or erroneous documentation be considered and filed as a bug more aggressively? There is a bug-category DOC, but it doesn't seem to be used very often. [2] There are several reasons to make this a good move: * The obvious quality improvement. * Documentation is a good start for people that want to get involved and have a look around the interpreter. * Documentation tasks can be picked up by people that are not the implementors. * Easier to keep track of the dark corners. Reasons against might be: * Could be considered as noise from developers/ticket-managers - especially when a feature is new i Florian Gilcher 2008-11-24T09:33:03 http://comments.gmane.org/gmane.comp.lang.ruby.core/19359 http://kurtstephens.com/node/72 Evaluating :‘foo_bar’ is 1.5 to 2.5 times faster than :foo_bar. This is true for both Ruby 1.8.6-p287 and Ruby 1.9 trunk. The most common means of specifying a Symbol literal is slower than the general expression to create a Symbol from a String constant. # Ruby 1.9 trunk. > ~/local/ruby/trunk/bin/ruby symbol_benchmark.rb user system total real :foo_bar 0.180000 0.000000 0.180000 ( 0.178016) :'foo_bar' 0.070000 0.000000 0.070000 ( 0.072418) :"foo_bar" 0.080000 0.000000 0.080000 ( 0.072390) "foo_bar".to_sym 0.340000 0.000000 0.340000 ( 0.340502) :"foo_#{'bar'}" 0.060000 0.000000 0.060000 ( 0.073382) "foo_#{'bar'}".to_sym 0.350000 0.000000 0.350000 ( 0.349321) # ruby 1.8.6 > ruby symbol_benchmark.rb user system total real :foo_bar 0.370000 0.140000 0.510000 ( 0.513998) :'foo_bar' 0.240000 0.090000 0.330000 ( 0.331501) :"foo_bar" 0.270000 0.06000 Kurt Stephens 2008-11-23T09:11:26 http://comments.gmane.org/gmane.comp.lang.ruby.core/19358 Hi -- In this code: => nil [1, 2, "c", 3] => [1, 2, "c", 3] I would expect [1, 3, "c", 2], because I would expect d (a required argument) to be handled before b (an optional argument). I know it's almost unthinkable that one would use this method signature, but I'd still like to understand the reasoning fully. I thought the idea was: handle the required arguments first, but it seems to be: move from left to right, looking ahead at every point to see whether there are enough arguments left and, at that point, give the right-hand required arguments priority. Is that right? David David A. Black 2008-11-23T09:00:25 http://comments.gmane.org/gmane.comp.lang.ruby.core/19357 I just added ruby 1.9 (svn rev 20317) to a simple xml processing benchmark I've created. So far I've only tested rexml on ruby 1.9 but was surprised to find it about 13% slower than ruby 1.8.6. In the benchmark (described below) ruby 1.9 took 9.793s while ruby 1.8.6 took only 8.606s. ---------------------------------------------------------------------------------- I've updated my simple ruby xml benchmark which measures the time to open a 98k XML document and count one type of leaf element (466 entries) 100 times. https://svn.concord.org/svn/projects/trunk/common/ruby/xml_benchmarks/ The summary is that for this one test using libxml in MRI 1.8.6 and jdom_document_builder (a native Java library) in JRuby take just about the same time. This is similar to the last time I ran these benchmarks. However testing in REXML, 8 months JRuby was 41% slower than MRI 1.8.6 while now it's about 35% faster. Tests run on a MacBook Pro, Mac OS X 10.5.5, 4GB memory, 2.5 GHz Intel Core 2 Duo. hpricot Stephen Bannasch 2008-11-23T04:27:13 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.lang.ruby.core