[#5322] O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...>

I just did some benchmarks on push, pop, shift, and unshift

24 messages 2005/07/01
[#5338] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/02

On Fri, 1 Jul 2005, Eric Mahurin wrote:

[#5348] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/02

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5357] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sat, 2 Jul 2005, Eric Mahurin wrote:

[#5359] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5361] Re: O(1) performance for insertions/deletions at the front of an Array/String — Mathieu Bouchard <matju@...> 2005/07/03

On Sun, 3 Jul 2005, Eric Mahurin wrote:

[#5362] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/03

--- Mathieu Bouchard <matju@artengine.ca> wrote:

[#5365] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5367] Re: O(1) performance for insertions/deletions at the front of an Array/String — Eric Mahurin <eric_mahurin@...> 2005/07/04

--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:

[#5368] Re: O(1) performance for insertions/deletions at the front of an Array/String — Yukihiro Matsumoto <matz@...> 2005/07/04

Hi,

[#5372] Re: O(1) performance for insertions/deletions at the front of an Array/String — Florian Gro<florgro@...> 2005/07/04

Yukihiro Matsumoto wrote:

[#5420] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...>

Sydney, an experimental ruby interpreter, has been released!

15 messages 2005/07/11
[#5424] Re: [ANN] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...> 2005/07/12

Thanks everyone for the feedback so far!

Re: [ANN] Sydney Developer Preview 1 released

From: nobu.nokada@...
Date: 2005-07-12 23:53:43 UTC
List: ruby-core #5436
Hi,

At Wed, 13 Jul 2005 03:10:17 +0900,
Evan Webb wrote in [ruby-core:05430]:
> > * macro _C in globals.h conflicted with one in ctype.h
> 
> Hmmm. On which platform? I dont have a _C macro under linux or freebsd.

I found it on cygwin.

> > * stringization by # needs ANSI C compiler
> 
> Could you elaborate?

  #define _C(kls) rb_path2class0(#kls)

Making string literals from macro arguments prefixed by # is
specified by ANSI standard, so older compilers may not support
the feature.

# And, // style comment is newer than it.

> > * using IDs as storages for temporary (and possibly long)
> >   strings would not be a nice idea.  ID names never get freed
> >   until the process dies.
> 
> Hm. Where do you see me doing that? With the _S() macro? The _S()
> macro just replaced global rb_intern()'d variables.

User defined % literals.

              case 1:
                lex_strterm = NEW_STRTERM(str_xquote, term, paren);
                pslval->id = rb_intern(tmpstr);
                return tXSTRING_BEG;

> > * there is a swap file of test/sydney/test_binding.rb
> 
> A swap file? Like it takes up a bunch of memory?

Just a junk file, sydney-dr1/test/sydney/.test_binding.rb.swp

> > And it contains so many and large changes, can't you split it
> > to some patches?
> 
> Yes, I can split it up. The vast bulk of the changes were required to
> get OS threads working properly, so all of that needs to be a single
> thread. I could easily split off the other features (Backtrace / Frame
> objects, other hooks, etc) into patchs.

As for Batktrace, I've been thinking about an iterator rather
than a method returning an array.

-- 
Nobu Nakada

In This Thread