[#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: make fail; ruby v182 not finding readline ?

From: Ben Schumacher <benschumacher@...>
Date: 2005-07-15 16:41:32 UTC
List: ruby-core #5472
On 7/15/05, OpenMacNews <OpenMacNews@speakeasy.net> wrote:
> ENV includes:
> 
>     setenv LDFLAGS "-L/usr/local -lreadline"
>     setenv CPPFLAGS "-I/usr/local"

On 7/15/05, OpenMacNews <OpenMacNews@speakeasy.net> wrote:
> hi all,
> 
> bldg ruby v182 on OSX 10.4.2
> 
> libreadline v50 is correctly built into /usr/local.
> 
> ENV includes:
> 
>     setenv LDFLAGS "-L/usr/local -lreadline"
>     setenv CPPFLAGS "-I/usr/local"

Have you tried doing this with this environment as well?

    setenv CFLAGS "-I/usr/local"

Cause it looks like that -I/usr/local isn't being used as part of the
build parameters here:

> but, 'make' fails @:
> 
>     ...
>     cc -dynamic -bundle -undefined suppress -flat_namespace  -L"../../.." -o
>     cparse.bundle cparse.o  -lruby  -lpthread -ldl -lcrypt -lobjc
>     compiling readline
>     gcc -fno-common -g -O2  -fno-common -pipe -fno-common
>     -DREADLINE_21_OR_LATER  -I. -I../.. -I../../. -I../.././ext/readline
>     -DHAVE_READLINE_READLINE_H -DHAVE_READLINE_HISTORY_H  -c readline.c
>     readline.c: In function 'filename_completion_proc_call':
>     readline.c:646: error: 'filename_completion_function' undeclared (first use
>     in this function)
>     readline.c:646: error: (Each undeclared identifier is reported only once
>     readline.c:646: error: for each function it appears in.)
>     readline.c:646: warning: assignment makes pointer from integer without a
>     cast
>     readline.c: In function 'username_completion_proc_call':
>     readline.c:673: error: 'username_completion_function' undeclared (first use
>     in this function)
>     readline.c:673: warning: assignment makes pointer from integer without a
>     cast
>     make[1]: *** [readline.o] Error 1
>     make: *** [all] Error 1
> 
> 
> NOTE: no trace of "-lreadline" ...

Cheers,

bs.


In This Thread