10553-10828

10325-15313 subjects 10752-11120

[ ruby-Bugs-9200 ] Problem with long regular expressions
10553 [noreply@ru y] Bugs item #9200, was opened at 12/03/2007 10:42

[ ruby-Bugs-9201 ] An array in a Hahs
10554 [noreply@ru y] Bugs item #9201, was opened at 2007-03-12 10:50
10555 [rubycore@ro ] This is as expected. The parameter to Hash#new is evaluated once, and

[ ruby-Bugs-9208 ] Ruby Gem installer not playing nice on Ubuntu
10560 [noreply@ru y] Bugs item #9208, was opened at 2007-03-12 16:19

[ANN] Ruby 1.8.6 has been released
10563 [knu@iD em ns] I am pleased to announce that Ruby 1.8.6, the latest release from the
+ 10565 [jan.svitok@g] haven't tested it more.
| 10566 [jan.svitok@g] I mean VS 2005 SP1 of course.
+ 10567 [Daniel.Berge] * New library: digest/bubblebabble
| 10568 [knu@iD em ns] Indeed I should have.  I'll keep it in mind for the future.
+ 10572 [hgs@dm .a .u] I'm getting failures on 2 sun-sparc-solaris9 systems, despite the

[ ruby-Bugs-9220 ] Time conversion from UTC to local appears to apply 2007 rules to 2006 dates
10564 [noreply@ru y] Bugs item #9220, was opened at 2007-03-12 16:19
10569 [nobu@ru y- a] It is an issue of the platform irrelevant to Ruby.

[ ruby-Bugs-9250 ] "each" function failed to detect element delete then jump a valid element when next yield.
10570 [noreply@ru y] Bugs item #9250, was opened at 2007-03-13 03:38
10571 [haisenko@co ] element when next yield.

[ ruby-Bugs-9261 ] BigDecimal initialisation bug
10573 [noreply@ru y] Bugs item #9261, was opened at 2007-03-13 17:32

1.8.6 timeut.rb segfault
10574 [hgs@dm .a .u] I've just received this message from cron.
10579 [nobu@ru y- a] Can't you show reproducable code, or backtrace?
10591 [hgs@dm .a .u] Yes, but it's from an erb job run by cron, and that's all I got from cron

'rescue' with non-exception class
10575 [B.Candler@po] I was just caught out by this odd behaviour: a 'rescue' clause doesn't
+ 10576 [vjoel@pa h. ] I think I've been bit by that one too. Timeout vs. TimeoutError.
+ 10577 [nobu@ru y- a] Modules also are allowed there.
+ 10617 [B.Candler@po] ... and a class is_a module. Obviously, a class which is a subclass of
  + 10618 [nobu@ru y- a] No, what is allowed there is a subclass of Exception, or an
  + 10628 [B.Candler@po] OK, interesting (and I'd never come across that feature). iconv is written

[ ruby-Patches-9272 ] [PATCH] Rdoc omitting docs for Module due to :stopdoc: directive in lib/yaml/tab.rb
10578 [noreply@ru y] Patches item #9272, was opened at 2007-03-13 19:43

Kernel#exec on OSX
10580 [ksruby@gm il] $ irb
+ 10581 [sur.max@gm i] ...
| 10582 [ksruby@gm il] Which is not what I'm looking for.
+ 10583 [shyouhei@ru ] It's a very difficult problem that can hardly be solved.
  10584 [ksruby@gm il] Thank you very much! That explains it.
  10590 [holon@ra as ] ...

Bugfix: Extension Compile Error with 1.8.6
10585 [mailinglists] i tried compile some extensions in a "cpp" C++ file. and the move of
+ 10586 [mailinglists] Please forget this message.
+ 10587 [nobu@ru y- a] Instead,
  10588 [mailinglists] No this doesn't help the problem is the line below.  "VALUE thread;"
  10589 [nobu@ru y- a] Sorry, I couldn't understand the error messages in your second post.
  10592 [mailinglists] Well it's Microsoft, so it's odd by definition ;-)

[ ruby-Patches-9280 ] Digest'ifying OpenSSL::Digest
10593 [noreply@ru y] Patches item #9280, was opened at 2007-03-14 21:44

[PATCH] grave bug in 1.8.6's thread implementation
10594 [sylvain.joye] ...
+ 10595 [mental@ry ia] fastthread originally had both behaviors, but I had to drop them because I got too many reports of existing Ruby code depending on thread.rb's behavior, where recursive locks block, and non-owners are able to unlock.
+ 10596 [mental@ry ia] Perhaps you attached the wrong file?  This looks like a variation on the not_owner patch.
  10597 [sylvain.joye] ...
  10598 [mental@ry ia] Hmm, why not just add a "prev" variable?
  10599 [sylvain.joye] ...
  10600 [mental@ry ia] Your fix looks good.
  10601 [sylvain.joye] ...
  10602 [mental@ry ia] Looks good.  You should probably post each of your patches (with descriptions of the problems they fix) to the Ruby bug tracker to make sure that they don't get lost.
  10603 [sylvain.joye] My experience w.r.t. the ruby tracker is that it seems hardly used, and
  10604 [mental@ry ia] My own experience (with multiple projects) has been that it's best to do both -- put the bug reports/patches in the tracker whilst also calling attention to them on the mailing list:  filing tracker entries without posting to the mailing list usually means that nobody notices, while posting to the mailing list without putting anything in the tracker usually means that nobody remembers.
  10608 [knu@iD em ns] Filing an issue to the tracker especially helps when many versions of
  10610 [sylvain.joye] ...
  10612 [mental@ry ia] FWIW, I agree with Sylvain on all these points.  The bugs addressed by the two necessary patches are subtle in manifestation (so many people have not noticed), but the locking primitives are simply not reliable unless they are addressed.
  10613 [hgs@dm .a .u] And I'm still getting my thread related segfault from my cron job, even

[ ruby-Bugs-9299 ] Thread are inheriting the priority of the starting thread
10607 [noreply@ru y] Bugs item #9299, was opened at 2007-03-15 08:17

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10609 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 09:35

unsubscribe
10611 [rdaubarede@a] unsubscribe

Re: Welcome to our (ruby-core ML) You are added automatically
10614 [agileanalysi] ...

Multiton in standard library
10615 [transfire@gm] I would like to propose that the Multiton pattern be supported in
10619 [tomp@ea th i] Is 'multiton' really the right name for this?  I've used a pattern
10620 [transfire@gm] And you are absolutely right. It is related to immutability --it is in
+ 10621 [james@gr yp ] I see these points and they are certainly correct, but honestly the
| + 10627 [transfire@gm] Yep, your example is the typical way to handle this _at first_. It's
| + 10630 [meinrad.rech] I prefer to use a proven implementation over hacking my own which i'd
|   10631 [transfire@gm] There are libs a lot fatter than this in the standard package. And
|   + 10635 [chr_news@gm ] I am not sure if your use case example is a good one. One can make the argument that +/- Infinity should be instances of distinct classes.
|   | 10644 [transfire@gm] I think whether my particular implementation for +/-Infinity is  a
|   + 10786 [james@gr yp ] I guess this pattern just doesn't come up for me as often as it does
+ 10622 [tomp@ea th i] Yes, I had seen that when I googled 'multiton'.  As wikipedia
  10623 [transfire@gm] I see. Well it's not your most common pattern, clearly. And I have
  + 10624 [vjoel@pa h. ] Maybe so, but that name always make me think of trucks.... It sounds
  | 10629 [rick.denatal] ROTFLMAO!
  + 10625 [tomp@ea th i] Actually, I think it's probably fairly common.  As you agreed, it's
    10626 [transfire@gm] Boy, I'm all rim today. Yea, of course, you're right. They're only

Is there interest in this? : get object from its object-specific class?
10616 [rick.denatal] The following is the culmination of a discussion on ruby-talk from a

[ ruby-Bugs-9353 ] xmlrpc keepalive connection bug
10632 [noreply@ru y] Bugs item #9353, was opened at 2007-03-18 16:21

[ ruby-Bugs-9359 ] Set.freeze not behaving as expected
10633 [noreply@ru y] Bugs item #9359, was opened at 2007-03-18 17:22

[ ruby-Bugs-9360 ] Matrix inverse problem
10634 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10636 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 14:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10637 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10638 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 14:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10639 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 14:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10640 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10641 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10642 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10643 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 23:41

re_set_syntax in libruby
10645 [hramrach@ce ] For me the re_set_syntax symbol in libruby clashes with another regex

[ ruby-Bugs-9376 ] Marshal.dump shouldn't complain about singletons if the _dump method is defined
10646 [noreply@ru y] Bugs item #9376, was opened at 2007-03-19 15:58
10647 [shyouhei@ru ] Yes.
10648 [sylvain.joye] Well ... maybe you can explain a bit more the "why" ...
10651 [matz@ru y- a] Because objects with singleton data can not be shared across
10665 [cdcarter@gm ] But what if that singleton class just contained a method that allowed
10667 [matz@ru y- a] I am not sure if we know what we are doing here.  Dumping objects
10675 [sylvain.joye] I don't see why as soon as the dumping/loading is done by user code. I
+ 10676 [matz@ru y- a] In most of my use case, singleton behavior/attribute is fundamental to
| + 10678 [sylvain.joye] _dump is not explicitely defined on ARGF. I don't have any problem with
| | 10679 [matz@ru y- a] I think I misread your report.  Sorry.
| + 10685 [matz@ru y- a] I fixed and committed in to the repository.  You will never see
+ 10682 [jim@fr ez .o] When I need to marshal an object that contains a simple singleton,

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10649 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 04:35

[ ruby-Bugs-3927 ] Buffer error installing gems using Zlib 1.2.1 on Windows
10650 [noreply@ru y] Bugs item #3927, was opened at 2006-03-27 12:59

[ ruby-Bugs-5319 ] rdoc documents C module methods as instance methods (patch)
10652 [noreply@ru y] Bugs item #5319, was opened at 2006-08-05 12:13

[ ruby-Bugs-6453 ] rdoc --fmt=html throws Segmentation faults
10653 [noreply@ru y] Bugs item #6453, was opened at 2006-11-02 05:49

[ ruby-Bugs-6370 ] RDoc for Kernel#select same as IO.select
10654 [noreply@ru y] Bugs item #6370, was opened at 2006-10-27 21:36

[ ruby-Bugs-3866 ] [PATCH] rdoc for String#=~
10655 [noreply@ru y] Bugs item #3866, was opened at 2006-03-19 12:18

[ ruby-Bugs-5740 ] RDOC doesn't show string  "#" or "\#"
10656 [noreply@ru y] Bugs item #5740, was opened at 2006-09-13 04:55

[ ruby-Bugs-6443 ] ri for specific method returns suggestion to refine search if there are similarly named methods
10657 [noreply@ru y] Bugs item #6443, was opened at 2006-11-01 13:19

[ ruby-Bugs-5563 ] rdoc/usage uses an uninitalized constant
10658 [noreply@ru y] Bugs item #5563, was opened at 2006-08-29 13:18

[ ruby-Bugs-5921 ] "ri Array.new" doesn't show assignment values
10659 [noreply@ru y] Bugs item #5921, was opened at 2006-09-26 22:52

[ ruby-Bugs-4467 ] RDoc looks for doc headers at function prototypes
10660 [noreply@ru y] Bugs item #4467, was opened at 2006-05-13 04:50
10684 [Daniel.Berge] @@ -626,10 +626,18 @@

[ ruby-Bugs-3866 ] [PATCH] rdoc for String#=~
10661 [noreply@ru y] Bugs item #3866, was opened at 2006-03-19 12:18

[ ruby-Bugs-9359 ] Set.freeze not behaving as expected
10662 [noreply@ru y] Bugs item #9359, was opened at 2007-03-19 02:22

Array#initialize: Better error reporting
10663 [lists@be tr ] irb(main):001:0> RUBY_VERSION
+ 10664 [murphy@ru yc] this is funny :) :a is just interpreted as an integer here.
+ 10666 [matz@ru y- a] It is compatibility behavior.  It will be fixed in 1.9.  And -w will
  10668 [knu@iD em ns] Yeah, compatibility with good ol' Ruby 1.4 and prior. ;)

[ ruby-Bugs-9360 ] Matrix inverse problem
10669 [noreply@ru y] Bugs item #9360, was opened at 2007-03-19 07:41

[ ruby-Bugs-9360 ] Matrix inverse problem
10670 [noreply@ru y] Bugs item #9360, was opened at 2007-03-18 14:41

__method__ and __callee__
10671 [gwtmp01@ma .] It looks like __method__ and __callee__ got lost in
10674 [matz@ru y- a] Done, partially.  __callee__ does not work yet to get alias name.
10680 [transfire@gm] Any chance of getting away from "shadow methods"? In this case an

Re: How to get the name of the executing method?
10672 [gwtmp01@ma .] There were two methods, __method__ and __callee__ in 1.9 for

[ ruby-Patches-9388 ] remove_one must preserve List invariants
10673 [noreply@ru y] Patches item #9388, was opened at 2007-03-20 01:04

[ ruby-Bugs-9392 ] exec fails when ruby is built with pthreads enabled
10677 [noreply@ru y] Bugs item #9392, was opened at 2007-03-19 23:58

[ ruby-Bugs-9392 ] exec fails when ruby is built with pthreads enabled
10681 [noreply@ru y] Bugs item #9392, was opened at 2007-03-20 16:58

Rubyforge access
10683 [ntalbott@gm ] Can someone grant me access to admin bugs in the Rubyforge project?
10694 [tom@in oe he] Sure, done!
10696 [ntalbott@gm ] Works great - thanks Tom!

[ ruby-Bugs-9410 ] Bignum.to_s fails for certain values and certain bases (1.8.6 regression)
10686 [noreply@ru y] Bugs item #9410, was opened at 2007-03-20 11:38

[ ruby-Bugs-9410 ] Bignum.to_s fails for certain values and certain bases (1.8.6 regression)
10687 [noreply@ru y] Bugs item #9410, was opened at 2007-03-20 11:38

[ ruby-Bugs-9410 ] Bignum.to_s fails for certain values and certain bases (1.8.6 regression)
10688 [noreply@ru y] Bugs item #9410, was opened at 2007-03-20 11:38

GEM Problem
10690 [ceo@ha th rn] ================================================================
10693 [halostatue@g] This is better asked on the rubygems-devel list; however, it is a

[ ruby-Bugs-9415 ] OpenURI should allow redirects from http -> https URLS
10691 [noreply@ru y] Bugs item #9415, was opened at 2007-03-20 16:34

[ ruby-Bugs-9416 ] net/https peer_cert returning nil
10692 [noreply@ru y] Bugs item #9416, was opened at 2007-03-20 15:38

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10695 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 04:35

[ ruby-Bugs-8026 ] YAML fails to parse its own input
10697 [noreply@ru y] Bugs item #8026, was opened at 2007-01-20 10:44

Extensions to ipaddr.rb
10698 [b.candler@po] I'd like to contribute the following extensions to ipaddr.rb
+ 10700 [sroberts@un ] Is this your intention?
| 10711 [B.Candler@po] # Returns a new ipaddr built by bitwise AND.
| + 10714 [sroberts@un ] Fair enough.
| + 10727 [B.Candler@po] Hmm. I guess these operators could do IPAddr.new() on their RHS, unless RHS
|   + 10728 [usa@ga ba ec] I think that comparing different versions of IP addresses should
|   + 10737 [jos@ca no k.] Agreed. This was just a 5 minute hack to demonstrate the idea. This capability
+ 10717 [usa@ga ba ec] Hmm, I have two more suggestions (sorry, without patch).
  10720 [jos@ca no k.] An IPAddr.entries instance method method that enumerates the IP addresses

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10699 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 09:35

[ ruby-Bugs-8384 ] Discrepancy between GetoptLong.new and documentation
10701 [noreply@ru y] Bugs item #8384, was opened at 2007-02-02 10:06
10702 [Daniel.Berge] Wait - people actually use that module? :-P
10703 [rubycore@ro ] Sure... what would be a good alternative?
10704 [Daniel.Berge] From the stdlib? I think optparse is generally preferred.

[OT] Google Summer of Code proposal.
10705 [pedro.delgal] Three days ago, i have send this sketch proposal to the ruby-talk
10706 [halostatue@g] You should post this on the Summer of Code website to the Ruby
10707 [pedro.delgal] I know but i would like some feedback before I want to send it today.
10710 [halostatue@g] Trust me; you'll get feedback from the mentors/evaluators (I'm one).

[ ruby-Bugs-5372 ] Float#round sample code documentation error
10708 [noreply@ru y] Bugs item #5372, was opened at 2006-08-10 03:50

[ ruby-Bugs-5990 ] Inheritance and Autorunner: Default_test causes a problem
10709 [noreply@ru y] Bugs item #5990, was opened at 2006-10-02 10:05

Ruby Method Signatures (was Re: Multiton in standard library)
10712 [rick.denatal] Thinking about this a bit, I'm not sure how much more information a
10715 [jos@ca no k.] This would be nice for some kinds of tracing. We have a Perl Trace library at
10716 [transfire@gm] I'm a little confused, What's output of this?
+ 10719 [jos@ca no k.] It prints a suitably indented execution trace showing caller and
+ 10732 [rick.denatal] I'm guessing that this is bound to the currently executing method, no?
  10739 [pbrannan@at ] I agree that the signature must contain at least the above information
  10753 [rick.denatal] My point though is that in common Computer Science terms, methods
  10756 [transfire@gm] Thats' true. The real need though is just so we can define method
  10758 [rick.denatal] Something like this might work, the only glitch is methods like
  10774 [transfire@gm] Yea, That's basically what I've been doing. It would be nice if we had

RCR - Sorry!
10713 [lists@be tr ] really bad and I detected the "Edit" button. I corrected the

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10718 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 04:35

[ ruby-Bugs-9451 ] Exception in Matrix inverse
10721 [noreply@ru y] Bugs item #9451, was opened at 2007-03-21 20:40

[ ruby-Bugs-9451 ] Exception in Matrix inverse
10722 [noreply@ru y] Bugs item #9451, was opened at 2007-03-21 20:40

[ ruby-Bugs-9451 ] Exception in Matrix inverse
10723 [noreply@ru y] Bugs item #9451, was opened at 2007-03-21 20:40

[ ruby-Bugs-9451 ] Exception in Matrix inverse
10724 [noreply@ru y] Bugs item #9451, was opened at 2007-03-21 20:40

[ ruby-Bugs-9451 ] Exception in Matrix inverse
10725 [noreply@ru y] Bugs item #9451, was opened at 2007-03-21 20:40

New Exploring Facility
10726 [ceo@ha th rn] ...
10775 [meinrad.rech] ...

[ ruby-Bugs-9462 ] BUGS in metaclasses inheritance
10729 [noreply@ru y] Bugs item #9462, was opened at 22/03/2007 11:19
10733 [ceo@ha th rn] ...
10736 [rick.denatal] Where did that come from?
10740 [ceo@ha th rn] ...

[ ruby-Bugs-9463 ] While executing gem ... (Gem::RemoteFetcher::FetchError)
10730 [noreply@ru y] Bugs item #9463, was opened at 2007-03-22 17:29

[ ruby-Bugs-9463 ] While executing gem ... (Gem::RemoteFetcher::FetchError)
10731 [noreply@ru y] Bugs item #9463, was opened at 2007-03-22 17:29

[ ruby-Bugs-9470 ] TempFile fails to delete the file if inside a Dir.chdir block
10734 [noreply@ru y] Bugs item #9470, was opened at 2007-03-22 16:28
10738 [Daniel.Berge] @@ -24,6 +24,8 @@

[ ruby-Bugs-9463 ] While executing gem ... (Gem::RemoteFetcher::FetchError)
10735 [noreply@ru y] Bugs item #9463, was opened at 2007-03-22 17:29

MyBad ==> Re: [ ruby-Bugs-9462 ] BUGS in metaclasses inheritance
10741 [ceo@ha th rn] JUST A NOTE -- I took out the "test_object" Instance and singleton for

Re: [ ruby-Bugs-9462 ] BUGS -- New Chart at Program Start
10742 [ceo@ha th rn] ...

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10743 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 03:35

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10744 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 03:35

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10745 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 03:35

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10746 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 03:35
10748 [nobu@ru y- a] Sorry, it's a weird side effect of the fix for [ruby-core:9675].
10760 [ntalbott@gm ] can you include it when you commit the fix?
10778 [ryand-ruby@z] I agree. This fix needs to go out. test::unit, autotest, multiruby,

[ ruby-Bugs-9300 ] sub-process with Test::Unit does not exit error code as expected
10747 [noreply@ru y] Bugs item #9300, was opened at 2007-03-15 03:35

class_extension
10749 [transfire@gm] I'm just following up to find out the status of consideration for
10750 [matz@ru y- a] I am not sure what class_extension or extension does.  Do they return
10751 [transfire@gm] You don't remember? It was your idea! Great, now I feel about this
10759 [matz@ru y- a] As you might already know, my memory is volatile. ;-)
+ 10773 [transfire@gm] That's true. I was just suggesting an alternate notation that seemed
+ 10828 [transfire@gm] Oh, I assure you, my memory is far worse!
threads.html
top