Array shift bug

Ruby
21

Hi,

In message “Re: Array shift bug”
on Wed, 27 Sep 2006 14:08:03 +0900, “Eric M.”
[email protected] writes:

|I tried out the code and it looks better in a few spots, but it also got
|worse in a few (but not as common). You can still use enormous amounts of
|memory because of the copy-on-write mechanism. I am attaching a testbench
|for testing runtime and memory (sorry, linux only) performance for a bunch
|of array operations that can be O(1). It also includes some new tests at
|the end (didn’t have these before) that show O(n**2) memory when it should
|be O(n). All of those performance (memory and runtime) issues were fixed in
|my patch.

I will examine your patch again. But I am afraid I was looking at the
old one. Could you show me your patch again?

						matz.
22

Hi,

In message “Re: Array shift bug”
on Thu, 28 Sep 2006 13:54:39 +0900, “Eric M.”
[email protected] writes:

|> I will examine your patch again. But I am afraid I was looking at the
|> old one. Could you show me your patch again?

|Would you check your email at matz at ruby dash lang dot org? I was not
|able to post the patch here because of the size. Let me know if there is a
|better address to send this.

I got it. I will examine. Thank you.

For the record, ruby-talk restrict mail size up to 300K or so to avoid
spams and viruses.

						matz.