[#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
On Fri, 1 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
On Sat, 2 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
On Sun, 3 Jul 2005, Eric Mahurin wrote:
--- Mathieu Bouchard <matju@artengine.ca> wrote:
Hi,
--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
Hi,
Yukihiro Matsumoto wrote:
--- Florian Gro<florgro@gmail.com> wrote:
Eric Mahurin wrote:
--- Nikolai Weibull
Eric Mahurin wrote:
[#5388] Problem with socket communications on Windows — "Jim McMaster" <jim.mcmaster@...>
I recently installed PGP 9.0 on my Windows XP SP2 machine. At that point,
[#5391] Object#=~ — Ryan Davis <ryand-ruby@...>
Since Rexexp#=~ and String#=~ return nil if they fail to match,
Hi,
Hi,
--- Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
[#5409] socket.c - s_recvfrom — Zach Dennis <zdennis@...>
If I am reading s_recvfrom correctly in can throw an error which kills
[#5420] Sydney Developer Preview 1 released — Evan Webb <evanwebb@...>
Sydney, an experimental ruby interpreter, has been released!
Thanks everyone for the feedback so far!
Hi,
The MD5 sum is 53d1bde4542365caf4849c56e6274617.
Hi,
On 7/12/05, nobuyoshi nakada <nobuyoshi.nakada@ge.com> wrote:
Hi,
Hello,
[#5445] GC tweak — Stefan Kaes <skaes@...>
I have found that the performance of current garbage collector
[#5451] bug in pstore (ruby 1.8.2) on Windows ( Win XP) ? — noreply@...
Bugs item #2101, was opened at 2005-07-14 15:30
[#5470] Bogus age value from Etc — Daniel Berger <Daniel.Berger@...>
Hi all,
[#5471] make fail; ruby v182 not finding readline ? — OpenMacNews <OpenMacNews@...>
hi all,
[#5476] Bug in ruby's command line parsing — Lothar Scholz <mailinglists@...>
Hello,
On Sat, Jul 16, 2005 at 10:11:34AM +0900, Lothar Scholz wrote:
[#5492] ruby ( v183) bcc32: using Socket.new with timeout -> files not closed — noreply@...
Bugs item #2131, was opened at 2005-07-19 17:34
Compile of ext\ripper\ripper.c fails during 1.9 [bccwin] build
Hi, ripper.c in 1.9.0 (2005/06/28) gives the following errors from a bcc 5.5 compile: -------------------------- Error E2342 ripper.y 4396: Type mismatch in parameter 'msg' (wanted 'const signed char *', got 'undefined') in function parser_yyerror [...] Error E2342 ripper.y 8833: Type mismatch in parameter 's' (wanted 'const signed char *', got 'undefined') in function ripper_intern Error E2356 ripper.y 8854: Type mismatch in redeclaration of 'ripper_compile_error' Error E2344 ripper.y 406: Earlier declaration of 'ripper_compile_error' Error E2342 ripper.y 8868: Type mismatch in parameter 'fmt' (wanted 'const signed char *', got 'undefined') in function ripper_warn0 Error E2342 ripper.y 8877: Type mismatch in parameter 'fmt' (wanted 'const signed char *', got 'undefined') in function ripper_warnI Error E2342 ripper.y 8887: Type mismatch in parameter 'fmt' (wanted 'const signed char *', got 'undefined') in function ripper_warnS Error E2342 ripper.y 8887: Type mismatch in parameter 'str' (wanted 'const signed char *', got 'undefined') in function ripper_warnS Error E2342 ripper.y 8896: Type mismatch in parameter 'fmt' (wanted 'const signed char *', got 'undefined') in function ripper_warning0 -------------------------- HAVE_STDARG_PROTOTYPES is defined. 1.9.0-2005.06.28\bccwin32>set BISON_SIMPLE=D:\UNIX\usr\local\share\bison.simple 1.9.0-2005.06.28\bccwin32>make bison 1.28 is from http://unxutils.sourceforge.net/ ( #line 3 "/usr/local/share/bison.simple" /* This file comes from bison-1.28. */ ) To build Ruby, I bypassed ripper because I hadn't time to debug it but I wonder if it's related to this macro: #define parser ((struct parser_params*)parser_v) ... and its effect on a function declaration containing an argument with the name "parser": static void ripper_compile_error(struct parser_params *parser, const char *fmt, ...) I would expect the preprocessor to expand it to this horrible mess: static void ripper_compile_error(struct parser_params *((struct parser_params*)parser_v), const char *fmt, ...) ... which is a redeclaration (doesn't match the prototype) and a "type mismatch". The ripper_warn___() functions also have "parser" in their argument names. Some of the other errors may be caused as a result. If needed, e-mail tar.gz compiler tests to daz[@]d10[.]karoo[.]co[.]uk . I hope this is helpful to Aoki-san. daz