[#29270] Proposal: Module#thunk_method — Charles Oliver Nutter <headius@...>

Many people use define_method solely so they can define a new method

13 messages 2010/04/06

[#29293] URI.(un)escape deprecated? — Marc-Andre Lafortune <ruby-core-mailing-list@...>

Hi.

16 messages 2010/04/07
[#29366] Re: URI.(un)escape deprecated? — Tanaka Akira <akr@...> 2010/04/08

2010/4/7 Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca>:

[#29313] [Bug #3112] require "yaml" doesn't use psych as default — Usaku NAKAMURA <redmine@...>

Bug #3112: require "yaml" doesn't use psych as default

28 messages 2010/04/08
[#29315] [Bug #3112] require "yaml" doesn't use psych as default — Yui NARUSE <redmine@...> 2010/04/08

Issue #3112 has been updated by Yui NARUSE.

[#29336] Re: [Bug #3112] require "yaml" doesn't use psych as default — Aaron Patterson <aaron@...> 2010/04/08

On Thu, Apr 08, 2010 at 02:06:55PM +0900, Yui NARUSE wrote:

[#29395] [Bug #3119] [Patch] "IOError (closed stream)" error with tempfile unlink then close usage — Simon Nicholls <redmine@...>

Bug #3119: [Patch] "IOError (closed stream)" error with tempfile unlink then close usage

9 messages 2010/04/09

[#29427] [Bug #3124] SocketError on SnowLeopard (during make test-all) — Aaron Patterson <redmine@...>

Bug #3124: SocketError on SnowLeopard (during make test-all)

10 messages 2010/04/11

[#29462] [Feature #3131] add Kernel#Hash() method like Kernel#Array() — Suraj Kurapati <redmine@...>

Feature #3131: add Kernel#Hash() method like Kernel#Array()

10 messages 2010/04/11

[#29464] [Bug #3132] …/nokogiri-1.4.1/ext/nokogiri/nokogiri.bundle: [BUG] Bus Error — Ashley Williams <redmine@...>

Bug #3132: …/nokogiri-1.4.1/ext/nokogiri/nokogiri.bundle: [BUG] Bus Error

8 messages 2010/04/12

[#29486] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Aaron Patterson <redmine@...>

Bug #3140: gem activation has changed between 1.8 and 1.9

102 messages 2010/04/13
[#31002] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Aaron Patterson <redmine@...> 2010/07/02

Issue #3140 has been updated by Aaron Patterson.

[#31003] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke ENDOH <mame@...> 2010/07/02

Hi,

[#31005] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yehuda Katz <wycats@...> 2010/07/02

We are about to ship a version of Ruby with a built in package manager with

[#29489] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Evan Phoenix <evan@...> 2010/04/13

After a brief discussion with Eric Hodel about this, there are a few questions before we can figure out how to solve this:

[#29513] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Evan Phoenix <evan@...> 2010/04/14

Is there any comment on this? This is a big bug in 1.9.2 that we'd like to get fixed as soon as we can, but I need some input on it.

[#29526] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Rich Kilmer <rich.kilmer@...> 2010/04/15

I wrote this original code in gem_prelude.

[#31104] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke Endoh <redmine@...> 2010/07/07

Issue #3140 has been updated by Yusuke Endoh.

[#31108] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Roger Pack <rogerdpack2@...> 2010/07/07

> I've commited the patch to trunk.

[#31193] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yusuke ENDOH <mame@...> 2010/07/11

Hi,

[#31223] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Roger Pack <rogerdpack2@...> 2010/07/12

> Roger, could you re-try to build from scratch? ould you apply

[#31215] [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yehuda Katz <redmine@...> 2010/07/12

Issue #3140 has been updated by Yehuda Katz.

[#31218] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9 — Yukihiro Matsumoto <matz@...> 2010/07/12

Hi,

[#29528] [Bug #3150] net/https peer verification doesn't do anything — Hongli Lai <redmine@...>

Bug #3150: net/https peer verification doesn't do anything

11 messages 2010/04/15

[#29578] [Bug #3163] SyntaxError when using variable which is also a method in current scope with a Symbol argument — Benoit Daloze <redmine@...>

Bug #3163: SyntaxError when using variable which is also a method in current scope with a Symbol argument

17 messages 2010/04/17
[#29583] [Bug #3163] SyntaxError when using variable which is also a method in current scope with a Symbol argument — caleb clausen <redmine@...> 2010/04/18

Issue #3163 has been updated by caleb clausen.

[#29641] [Feature #3176] Thread#priority= should actually do something — caleb clausen <redmine@...>

Feature #3176: Thread#priority= should actually do something

28 messages 2010/04/19

[#29710] [Bug #3185] File.expand_path repeats forward slashes at the beginning of the path — Brian Ford <redmine@...>

Bug #3185: File.expand_path repeats forward slashes at the beginning of the path

10 messages 2010/04/21

[#29835] [Bug #3212] ConditionVariable may become inconsistent for interrupted threads — Sylvain Joyeux <redmine@...>

Bug #3212: ConditionVariable may become inconsistent for interrupted threads

24 messages 2010/04/28

[#29868] [Bug:trunk] assert now passes non-boolean result — Nobuyoshi Nakada <nobu@...>

Hi,

15 messages 2010/04/29

[ruby-core:29465] Re: [RubySpec #3128] Randomness specs

From: Caleb Clausen <vikkous@...>
Date: 2010-04-12 01:07:32 UTC
List: ruby-core #29465
On 4/11/10, Marc-Andre Lafortune <ruby-core-mailing-list@marc-andre.ca> wrote:
> Hi,
>
> On Sun, Apr 11, 2010 at 1:30 PM, Caleb Clausen <vikkous@gmail.com> wrote:
>> I find this troubling, since it could imply that the random number
>> generator obeys the mythical law of averages. You know better, I'm
>> sure, but others may not. A written standard needs to be very clear
>> about this, and use the appropriate statistical language.
>
> If I knew better, I would probably refer to a known statistical test :-)

Yeah, me too.
The appropriate language should be something like:

After M>>N iterations, the probability that all integers in the range
0...N have been seen should be [[some number only slightly smaller
than one, calculated from M and N, exact formula not clear to me right
now]].

> I just meant that rubinius' implementation is such that Kernel.rand(1
> << 64) will never return any value greater than 1 << 31, which I find
> troubling.

Yeah, that's clearly wrong.

>> 5) could be interpreted 2 ways, depending on the meaning of the
>> ambiguous term 'platform'.
>
> Indeed, sorry about the poor wording. I meant in the stronger sense,
> i.e. on all implementations and all platforms (your 5b)

I think we're still not reading from the same page on this... :)

Reading back over your message, it's clear that you meant from 5)
something like: the Random class (and Kernel#rand) must behave exactly
like MRI's Random under all circumstances. That's far too stringent of
a requirement in my opinion.

What I originally thought you meant, (maybe Nobu too) was that a
particular implementation's Random should be consistent with itself;
it should always return the same sequence given the same seed
regardless of what OS (or JVM, say) it's running under. Thus, JRuby's
Random should return the same random sequence whether its running
under windows, linux, sunos, blackstone, whatever. But it need not
return the same sequence as MRI on those same platforms.

> So, what should apply to the Ruby language?

Here's my opinion:

Random numbers should appear to be random, given some reasonable
minimum set of TBD randomness tests. It's easily possible to get too
crazy with the RNG tests. (The most complete test for random numbers I
have seen is diehard [1] (written in fortran, and doesn't give clear
pass/fail result, unfortunately.... which is a problem with RNG tests
generally). [2] is also somewhat helpful.) This is what you're driving
at with 0) 1) and 2).

[2] suggests chi-squared tests, which is probably reasonable. (I don't
actually understand the math behind this... also this test also does
not give a clear pass/fail result...)

In addition, there should probably be some language like this:

  Random MUST NOT (SHOULD NOT?) use a known weak random number
generator, such as the linear congruential generator.
  Random SHOULD use Mersenne Twister, since this is simple to
implement and the state of the art in PRNGs at the time of writing.
Random MAY use a better algorithm than MT if such an algorithm is
invented in the future.


[1] ftp://stat.fsu.edu/pub/diehard (not working ATM)
[2] http://burtleburtle.net/bob/rand/testsfor.html

In This Thread