ruby-core

[#1575] String#gsub bug? — "Gavin Sinclair" <gsinclair@...>

Is this a bug in Ruby or a bug in my brain? I've stared at it for long

3 messages 2003/10/03

[#1577] Re: String#gsub bug? — bruceb3@... 2003/10/03

On Fri, Oct 03, 2003 at 03:34:46PM +0900, Gavin Sinclair wrote:

[#1578] Re: String#gsub bug? — "Gavin Sinclair" <gsinclair@...> 2003/10/03

> On Fri, Oct 03, 2003 at 03:34:46PM +0900, Gavin Sinclair wrote:

[#1576] Re: String#gsub bug? — Elliott Hughes <ehughes@...>

* means zero or more. Looks like that matched zero. Try + (one or more)

1 message 2003/10/03

[#1579] arity bug? — "Christoph" <chr_news@...>

Hi,

5 messages 2003/10/05

[#1580] Re: arity bug? — ts <decoux@...> 2003/10/05

>>>>> "C" == Christoph <chr_news@gmx.net> writes:

[#1581] Re: arity bug? — "Christoph" <chr_news@...> 2003/10/05

"ts" wrote:

[#1582] Re: arity bug? — matz@... (Yukihiro Matsumoto) 2003/10/05

Hi,

[#1594] Re: arity bug? — "Christoph" <chr_news@...> 2003/10/08

Yukihiro Matsumoto wrote:

[#1583] mkmf.rb fix — Mathieu Bouchard <matju@...>

2 messages 2003/10/06

[#1585] Re: mkmf.rb fix — matz@... (Yukihiro Matsumoto) 2003/10/06

Hi,

[#1584] C++ wrapper for Ruby interface? — Mathieu Bouchard <matju@...>

2 messages 2003/10/06

[#1587] Re: C++ wrapper for Ruby interface? — Stanislav Karchebny <berk@...> 2003/10/07

モママツンナホノノマヤ 6 鑠墹岱リ 2003 06:30 Mathieu Bouchard ホチミノモチフ(a):

[#1586] Yielding to a block from a proc? — Austin Ziegler <austin@...>

On irc://irc.freenode.net/#ruby-lang tonight we were discussing procs. Among

2 messages 2003/10/07

[#1590] Re: Yielding to a block from a proc? — Joel VanderWerf <vjoel@...> 2003/10/07

Austin Ziegler wrote:

[#1588] FreeBSD problem with processes — Laurent Sansonetti <pinux@...>

Hi all,

1 message 2003/10/07

[#1589] Success story. Ruby 1.8.0 + OpenSSL for Ruby 2 — Vladimir Shahov <v.shahov@...>

Hi

1 message 2003/10/07

[#1591] Re: Yielding to a block from a proc? — george.marrows@...

> > Is this right? Is this pathological? Is it a bug? Is there

6 messages 2003/10/08

[#1592] Re: Yielding to a block from a proc? — Sean Russell <ser@...> 2003/10/08

On Wednesday 08 October 2003 08:49, george.marrows@ps.ge.com wrote:

[#1601] Re: Yielding to a block from a proc? — "Christoph" <chr_news@...> 2003/10/09

Sean Russell wrote:

[#1602] Re: Yielding to a block from a proc? — Sean Russell <ser@...> 2003/10/09

On Thursday 09 October 2003 15:29, Christoph wrote:

[#1593] Re: Yielding to a block from a proc? — "Christoph" <chr_news@...> 2003/10/08

Sean Russell wrote:

[#1595] Re: Yielding to a block from a proc? — Sean Russell <ser@...> 2003/10/08

On Wednesday 08 October 2003 16:00, Christoph wrote:

[#1596] PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...>

Hello,

7 messages 2003/10/09

[#1597] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — matz@... (Yukihiro Matsumoto) 2003/10/09

Hi,

[#1598] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — Ryan Davis <ryand@...> 2003/10/09

[#1599] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...> 2003/10/09

On Fri, 10 Oct 2003 01:38:10 +0900, Ryan Davis wrote:

[#1606] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...> 2003/10/10

On Fri, 10 Oct 2003 00:27:23 +0900, Yukihiro Matsumoto wrote:

[#1607] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — matz@... (Yukihiro Matsumoto) 2003/10/10

Hi,

[#1608] Re: PATCH: Revive NextStep, OpenStep, Rhapsody ports — Eric Sunshine <sunshine@...> 2003/10/10

On Sat, 11 Oct 2003 01:11:35 +0900, Yukihiro Matsumoto wrote:

[#1600] CVS access — Sean Russell <ser@...>

Hiya,

8 messages 2003/10/09

[#1603] Re: CVS access — matz@... (Yukihiro Matsumoto) 2003/10/09

Hi,

[#1604] Re: CVS access — "Sean E. Russell" <ser@...> 2003/10/10

-----BEGIN PGP SIGNED MESSAGE-----

[#1609] Re: CVS access — Chad Fowler <chad@...> 2003/10/10

[#1610] Re: CVS access — "Sean E. Russell" <ser@...> 2003/10/11

-----BEGIN PGP SIGNED MESSAGE-----

[#1629] Re: CVS access — "Akinori MUSHA" <knu@...> 2003/10/13

At Sat, 11 Oct 2003 06:10:09 +0900,

[#1628] Re: CVS access — "Akinori MUSHA" <knu@...> 2003/10/13

At Fri, 10 Oct 2003 02:42:50 +0900,

[#1630] Re: CVS access — Sean Russell <ser@...> 2003/10/13

On Monday 13 October 2003 15:37, Akinori MUSHA wrote:

[#1605] Re: Yielding to a block from a proc? — george.marrows@...

1 message 2003/10/10

[#1611] set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...>

I've reduced the error I reported in ruby-talk:84013 to the following code:

17 messages 2003/10/11

[#1612] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/11

>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:

[#1616] Re: set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...> 2003/10/11

ts [mailto:decoux@moulon.inra.fr] wrote:

[#1617] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/11

>>>>> "N" == Nathaniel Talbott <nathaniel@talbott.ws> writes:

[#1624] Re: set_trace_func/Array#fetch error — "daz" <dooby@...10.karoo.co.uk> 2003/10/12

[#1625] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/12

>>>>> "d" == daz <dooby@d10.karoo.co.uk> writes:

[#1618] Re: set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...> 2003/10/11

ts [mailto:decoux@moulon.inra.fr] wrote:

[#1620] Re: set_trace_func/Array#fetch error — nobu.nokada@... 2003/10/12

Hi,

[#1621] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/12

>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:

[#1622] Re: set_trace_func/Array#fetch error — nobu.nokada@... 2003/10/12

Hi,

[#1623] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/12

>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:

[#1626] Re: set_trace_func/Array#fetch error — "daz" <dooby@...10.karoo.co.uk> 2003/10/12

[#1627] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/12

>>>>> "d" == daz <dooby@d10.karoo.co.uk> writes:

[#1613] Re: set_trace_func/Array#fetch error — "daz" <dooby@...10.karoo.co.uk> 2003/10/11

[#1614] Re: set_trace_func/Array#fetch error — ts <decoux@...> 2003/10/11

>>>>> "d" == daz <dooby@d10.karoo.co.uk> writes:

[#1615] Re: set_trace_func/Array#fetch error — "Nathaniel Talbott" <nathaniel@...> 2003/10/11

daz [mailto:dooby@d10.karoo.co.uk] wrote:

[#1619] Re: set_trace_func/Array#fetch error — "daz" <dooby@...10.karoo.co.uk> 2003/10/11

[#1631] inconsistency with lexing number bases — Ryan Davis <ryand-ruby@...>

Why is:

3 messages 2003/10/15

[#1632] Re: inconsistency with lexing number bases — Ryan Davis <ryand-ruby@...> 2003/10/15

um... smoking crack. I think we were mixing up our interpreters between

[#1633] Re: [OT] inconsistency with lexing number bases — "daz" <dooby@...10.karoo.co.uk> 2003/10/15

[#1634] stringy range bug — "Christoph" <chr_news@...>

Hi,

6 messages 2003/10/15

[#1635] Re: stringy range bug — ts <decoux@...> 2003/10/15

>>>>> "C" == Christoph <chr_news@gmx.net> writes:

[#1636] Re: stringy range bug — "Christoph" <chr_news@...> 2003/10/15

ts wrote:

[#1637] Re: stringy range bug — matz@... (Yukihiro Matsumoto) 2003/10/16

Hi,

[#1638] Re: stringy range bug — matz@... (Yukihiro Matsumoto) 2003/10/16

Hi,

[#1639] Re: stringy range bug — Jim Freeze <jim@...> 2003/10/16

On Thursday, 16 October 2003 at 16:49:56 +0900, Yukihiro Matsumoto wrote:

[#1640] SystemStackError in embedding — Sentinel <sentinel27@...>

Hi, I am just now trying to embed ruby into my apprication

8 messages 2003/10/18

[#1641] Re: SystemStackError in embedding — Mark Wilson <mwilson13@...> 2003/10/18

[#1642] Re: SystemStackError in embedding — Sentinel <sentinel27@...> 2003/10/18

Am Sonntag, 19. Oktober 2003 00:39 schrieb Mark Wilson:

[#1643] Re: SystemStackError in embedding — Sentinel <sentinel27@...> 2003/10/19

[#1644] Re: SystemStackError in embedding — Mathieu Bouchard <matju@...> 2003/10/19

[#1645] Re: SystemStackError in embedding — Sentinel <sentinel27@...> 2003/10/19

[#1646] Re: SystemStackError in embedding — Mathieu Bouchard <matju@...> 2003/10/19

[#1647] Re: SystemStackError in embedding — Sentinel <sentinel27@...> 2003/10/19

> Assuming you're on i686-compatible chips, then this is a known bug that