[#9382] the sign of a number is omitted when squaring it. -2**2 vs (-2)**2 — <noreply@...>

Bugs item #6468, was opened at 2006-11-03 17:25

9 messages 2006/11/03

[#9385] merge YARV into Ruby — SASADA Koichi <ko1@...>

Hi,

42 messages 2006/11/04
[#9405] Re: merge YARV into Ruby — "Kirill Shutemov" <k.shutemov@...> 2006/11/06

On 11/4/06, SASADA Koichi <ko1@atdot.net> wrote:

[#9406] Re: merge YARV into Ruby — Sylvain Joyeux <sylvain.joyeux@...4x.org> 2006/11/06

On Monday 06 November 2006 16:01, Kirill Shutemov wrote:

[#9417] Re: merge YARV into Ruby — Sean Russell <ser@...> 2006/11/06

On Monday 06 November 2006 10:15, Sylvain Joyeux wrote:

[#9428] Re: merge YARV into Ruby — "Kirill Shutemov" <k.shutemov@...> 2006/11/06

On 11/6/06, Sean Russell <ser@germane-software.com> wrote:

[#9402] fast mutexes for 1.8? — MenTaLguY <mental@...>

Many people have been using Thread.critical for locking because Ruby

24 messages 2006/11/06

[#9450] Bikeshed: No more Symbol < String? — Kornelius Kalnbach <murphy@...>

Hi ruby-core!

21 messages 2006/11/07
[#9452] Re: Bikeshed: No more Symbol < String? — Yukihiro Matsumoto <matz@...> 2006/11/07

Hi,

[#9493] Future Plans for Ruby 1.8 Series — URABE Shyouhei <shyouhei@...>

This week Japanese rubyists were talking about the future of ruby_1_8

13 messages 2006/11/09

[#9515] External entropy pool for random number generator — "Kirill Shutemov" <k.shutemov@...>

In the attachment patch which allow to use external entropy pool for

13 messages 2006/11/11
[#9522] Re: External entropy pool for random number generator — "Nobuyoshi Nakada" <nobu@...> 2006/11/13

Hi,

[#9554] Ruby 1.[89].\d+ and beyond. — Hugh Sasse <hgs@...>

I've been thinking about how version numbers are restricting what we can do.

30 messages 2006/11/16
[#9561] Re: Ruby 1.[89].\d+ and beyond. — Eric Hodel <drbrain@...7.net> 2006/11/16

[#9563] Re: Ruby 1.[89].\d+ and beyond. — Hugh Sasse <hgs@...> 2006/11/16

On Fri, 17 Nov 2006, Eric Hodel wrote:

[#9564] Re: Ruby 1.[89].\d+ and beyond. — Eric Hodel <drbrain@...7.net> 2006/11/16

On Nov 16, 2006, at 12:02 PM, Hugh Sasse wrote:

[#9571] Re: Ruby 1.[89].\d+ and beyond. — "Robert Dober" <robert.dober@...> 2006/11/19

On 11/16/06, Eric Hodel <drbrain@segment7.net> wrote:

[#9604] #ancestors never includes the singleton class (inconsistent) — <noreply@...>

Bugs item #6820, was opened at 2006-11-22 08:49

12 messages 2006/11/22
[#9618] Re: [ ruby-Bugs-6820 ] #ancestors never includes the singleton class (inconsistent) — Yukihiro Matsumoto <matz@...> 2006/11/25

Hi,

[#9629] Re: [ ruby-Bugs-6820 ] #ancestors never includes the singleton class (inconsistent) — Sylvain Joyeux <sylvain.joyeux@...4x.org> 2006/11/27

> It is supposed to. Singleton classes (or eigenclasses, if you want to

Re: merge YARV into Ruby

From: "Brian Mitchell" <binary42@...>
Date: 2006-11-06 22:39:22 UTC
List: ruby-core #9444
On 11/6/06, Joshua Haberman <joshua@reverberate.org> wrote:
> On Mon, 2006-11-06 at 13:55, Brian Mitchell wrote:
> > I agree enough with some of that though I wouldn't say Darcs doesn't
> > scale well (in comparison to svn) at this point.
>
> After I heard about the "poison patch" problem with Darcs, I basically
> stopped using it immediately and considered it unsuitable for pretty
> much anything.  I don't know how well-documented this problem is, but
> here is how one random person describes it:
>
> http://sayspy.blogspot.com/2006/08/comparing-mercurial-to-bazaar-ng.html
>
> "Well, Darcs suffer from a little advertised problem, known as the
> "poison patch". With a Darcs repo, you can end up in a situation where a
> particular checkout will take hours to days (and maybe eventually fail).
> This happened to one of my important Darcs-controlled project, and I can
> assure you that once it happened, you don't want to happen again. I
> should add that it is not predictable, so it can happen anytime."
>
> Yes, this is a informal comment on someone's blog, but I also see the
> problem referred to in this post to darcs-users, along with a proposal
> to address the problem:
>
> http://www.abridgegame.org/pipermail/darcs-users/2006-February/009454.html
>
> "I think there is a
> lot of potential here, but kept my initial proposal very basic and the
> minimum to help prevent the 'poison patch' problem which has been a
> serious issue in practice."
>
> I know my sources are somewhat hearsay, but I find this problem
> believable given what I know about Darcs and its theory of patches.  I
> would be very wary of trusting anything to a system that unpredictably
> becomes unusable.

After some research into the topic:

That problem is real but it is quite misrepresented in the blog post.
Poison patches are a generalized name for a few problems that emerge
from bad practices or sloppy management. Here is a FAQ entry that
notes the few problems that cause such things:

http://darcs.net/DarcsWiki/FrequentlyAskedQuestions#head-76fb029ff6e9c20468eacf3ff00d791e2cf03ecb

I've not had problems myself but they are there. Darcs is different
enough that some people feel like it is random. Fortunately, it seems
documented enough to avoid or at least solve.

Brian.

In This Thread