[#11383] Re: $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Daz,
[#11396] Re: $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Sylvain,
[#11401] Proc.== — David Flanagan <david@...>
Can anyone construct two proc objects p1 and p2, without using clone or
Hi,
Okay, anything other than the degenerate case of a proc with no body?
On Jun 4, 2007, at 22:57, David Flanagan wrote:
[#11409] Method introspection ? — "Jonas Pfenniger" <zimbatm@...>
Hello,
[#11418] currying in Ruby — David Flanagan <david@...>
I've written a little argument currying module for Procs and Methods. I
[#11431] Are there a better set of unit tests for Array? — "John Lam (CLR)" <jflam@...>
It seems like the unit tests that we have in Ruby.net were:
[#11439] comments needed for Random class — "NAKAMURA, Hiroshi" <nakahiro@...>
-----BEGIN PGP SIGNED MESSAGE-----
On 6/12/07, NAKAMURA, Hiroshi <nakahiro@sarion.co.jp> wrote:
[#11450] Re: new method dispatch rule (matz' proposal) — David Flanagan <david@...>
This is a late response to the very long thread that started back in
On 6/13/07, David Flanagan <david@davidflanagan.com> wrote:
On 6/13/07, David Flanagan <david@davidflanagan.com> wrote:
[#11457] Inclusion of bug #9376 in 1.8.6 branch — Sylvain Joyeux <sylvain.joyeux@...4x.org>
Would it be possible to include the fix for bug #9376 in 1.8.6 ? It is not
[#11462] What should this code do? — "John Lam (CLR)" <jflam@...>
Thinking about control flow these days ...
[#11472] Strange Array#transpose behavior for custom to_ary method — Daniel Berger <djberg96@...>
Ruby 1.8.6 p36
[#11481] Ancestors for Singleton classes — "Robert Dober" <robert.dober@...>
I am taking this away from ruby-talk as it contains patches.
[#11482] Ruby Changes Its Mind About Non-Word Characters — James Edward Gray II <james@...>
Does this look like a bug to anyone else?
James Edward Gray II wrote:
Hi,
On Jun 16, 2007, at 2:41 PM, Vincent Isambart wrote:
> > It is because the and サ characters are not in ISO-8859-1.
[#11505] Question about the patchlevel release cycle — Sylvain Joyeux <sylvain.joyeux@...4x.org>
1.8.6 thread support was broken in bad ways. It stayed for three months
> could you refer to bug #s?
Hi,
Hi, I'm the 1.8.6 branch manager.
On 6/20/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
[#11533] method_missing for Enumerator — TRANS <transfire@...>
What do others think of this for 1.9+?
[#11543] Re: Apple reportedly to ship with ruby 1.8.6-p36 unless informed what to patch — James Edward Gray II <james@...>
On Jun 27, 2007, at 4:47 PM, Bill Kelly wrote:
Hi,
On Jun 30, 2007, at 4:51 AM, Urabe Shyouhei wrote:
Hi,
Hi,
Hi,
I haven't seen it mentioned explicitly in this thread so far, but I
[#11545] Proc initialize method not called under certain circumstances — "John Lam (CLR)" <jflam@...>
class Proc
On Fri, 29 Jun 2007 05:43:14 +0900, "John Lam (CLR)" <jflam@microsoft.com> wrote:
So, is it correct to assume that for language constructs that create built-in types like Range, Array, Hash etc that user-defined initialize methods are never called?
Re: UPDATED: Building 1.8.6-p36 with Sun Studio 12 compiler
Please send reports like this to ruby-core, where they can make a difference. Forwarding... On Jun 14, 2007, at 11:55 , markea01@sbcglobal.net wrote: > All - > I have resolved most of the problems encountered during "make > check"; it seems the test runs do not honor LD_LIBRARY_PATH, so I had > to symlink the libraries for openssl, gdbm and ncurses to /lib, and > then my results look like this > > Finished in 73.679603 seconds. > > 1) Failure: > test_delete(TestDBM) [./test/dbm/test_dbm.rb:332]: > <DBMError> exception expected but none was thrown. > > 2) Failure: > test_delete(TestGDBM) [./test/gdbm/test_gdbm.rb:442]: > <GDBMError> exception expected but none was thrown. > > 3) Failure: > test_s_open_error(TestGDBM) [./test/gdbm/test_gdbm.rb:200]: > <Errno::EACCES> exception expected but none was thrown. > > 4) Failure: > test_should_propagate_signaled(TestBeginEndBlock) [./test/ > ruby/ > test_beginendblock.rb:84]: > <nil> expected but was > <130>. > > 5) Failure: > test_s_open_error(TestSDBM) [./test/sdbm/test_sdbm.rb:123]: > <Errno::EACCES> exception expected but none was thrown. > > 6) Failure: > test_condvar_wait_not_owner(TC_Thread) [./test/thread/ > test_thread.rb:35]: > <ThreadError> exception expected but none was thrown. > > 1618 tests, 16599 assertions, 6 failures, 0 errors > gmake: *** [test-all] Error 1 > > So it appears that most of the compiler warning messages are in fact > harmless. I would like to understand though why "--enable-pthread" > causes the backtrace error in eval.c: > > eval.c > "eval.c", line 4482: warning: statement not reached > "eval.c", line 4517: warning: statement not reached > "eval.c", line 4644: warning: statement not reached > "eval.c", line 4702: warning: statement not reached > "eval.c", line 5151: warning: statement not reached > "eval.c", line 5614: warning: statement not reached > "eval.c", line 5740: warning: statement not reached > "eval.c", line 6251: identifier redeclared: backtrace > current : static function() returning unsigned long > previous: function(pointer to pointer to void, int) > returning int : "/usr/include/execinfo.h", line 41 > "eval.c", line 8612: warning: loop not entered at top > "eval.c", line 12004: warning: statement not reached > "eval.c", line 12446: warning: statement not reached > "eval.c", line 12818: warning: statement not reached > cc: acomp failed for eval.c > gmake: *** [eval.o] Error 2 > > It seems to modify the includes such that /usr/include/execinfo.h gets > included, when without the "--enable-pthread" it doesn't (or some > other define "hides" the definition of backtrace). > > Mark Almeida > >