ruby-core

Mailing Lists

ruby-list (For Ruby users, JA) ruby-dev (For Ruby developers, JA) ruby-core (For Ruby developers, EN) ruby-talk (For Ruby users, EN)

[#1] Welcome to the ruby-core mailing list — matz@... (Yukihiro Matsumoto)

Hi,

2 messages 2002/05/10

[#2] Re: Welcome to the ruby-core mailing list — "Akinori MUSHA" <knu@...> 2002/05/10

At Fri, 10 May 2002 17:54:29 +0900,

[#3] GC — Michal Rokos <m.rokos@...>

Hi,

2 messages 2002/05/11

[#4] Re: [Cleanup] GC — matz@... (Yukihiro Matsumoto) 2002/05/11

Hi,

[#5] Licence tags & tiny mini cleanup — Michal Rokos <m.rokos@...>

Hi,

1 message 2002/05/12

[#6] Warnings on Solaris — Lars Christensen <larsch@...>

2 messages 2002/05/13

[#8] Re: [patch] Warnings on Solaris — Michal Rokos <m.rokos@...> 2002/05/14

Hi,

[#7] Useless patch... — Michal Rokos <m.rokos@...>

Hi,

6 messages 2002/05/14

[#9] Re: Useless patch... — matz@... (Yukihiro Matsumoto) 2002/05/14

Hi,

[#11] Re: Useless patch... — matz@... (Yukihiro Matsumoto) 2002/05/14

Hi,

[#10] Re: Useless patch... — Michal Rokos <m.rokos@...> 2002/05/14

Hi,

[#12] Re: Useless patch... — matz@... (Yukihiro Matsumoto) 2002/05/15

Hi,

[#13] Re: Useless patch... — Joel VanderWerf <vjoel@...> 2002/05/15

Yukihiro Matsumoto wrote:

[#14] — Michal Rokos <m.rokos@...>

Hi,

6 messages 2002/05/15

[#18] Re: [BUG] — matz@... (Yukihiro Matsumoto) 2002/05/15

Hi,

[#28] Re: [BUG] — Michal Rokos <m.rokos@...> 2002/05/16

Hi,

[#15] Re: [BUG] — nobu.nokada@... 2002/05/15

Hi,

[#16] Re: [BUG] — Michal Rokos <m.rokos@...> 2002/05/15

Hi,

[#17] Re: [BUG] — nobu.nokada@... 2002/05/15

Hi,

[#19] Re: [BUG] thread failure after trap — nobu.nokada@...

Hi,

11 messages 2002/05/16

[#20] Re: [BUG] thread failure after trap — ts <decoux@...> 2002/05/16

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

[#21] Re: [BUG] thread failure after trap — nobu.nokada@... 2002/05/16

Hi,

[#22] Re: [BUG] thread failure after trap — ts <decoux@...> 2002/05/16

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

[#25] Re: [BUG] thread failure after trap — nobu.nokada@... 2002/05/16

Hi,

[#23] Re: [BUG] thread failure after trap — nobu.nokada@... 2002/05/16

Hi,

[#29] Re: [BUG] thread failure after trap — ts <decoux@...> 2002/05/16

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

[#30] Re: [BUG] thread failure after trap — nobu.nokada@... 2002/05/16

Hi,

[#24] Re: [BUG] thread failure after trap — ts <decoux@...> 2002/05/16

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

[#26] Re: [BUG] thread failure after trap — nobu.nokada@... 2002/05/16

Hi,

[#27] Re: [BUG] thread failure after trap — ts <decoux@...> 2002/05/16

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

[#31] Ruby obsolete — Michal Rokos <m.rokos@...>

Hello again,

5 messages 2002/05/22

[#34] Re: Ruby obsolete — matz@... (Yukihiro Matsumoto) 2002/05/23

Hi,

[#37] Re: Ruby obsolete — Michal Rokos <m.rokos@...> 2002/05/23

Hi,

[#38] Re: Ruby obsolete — matz@... (Yukihiro Matsumoto) 2002/05/23

Hi,

[#39] Re: Ruby obsolete — Michal Rokos <m.rokos@...> 2002/05/23

[#32] Long fmt? — Michal Rokos <m.rokos@...>

Hi,

2 messages 2002/05/22

[#35] Re: Long fmt? — matz@... (Yukihiro Matsumoto) 2002/05/23

Hi,

[#33] Array #2 — Michal Rokos <m.rokos@...>

Hi,

2 messages 2002/05/22

[#36] Re: [Cleanup] Array #2 — matz@... (Yukihiro Matsumoto) 2002/05/23

Hi,

[#40] ToDo details? — Michal Rokos <m.rokos@...>

Hi,

2 messages 2002/05/23

[#41] Re: ToDo details? — matz@... (Yukihiro Matsumoto) 2002/05/23

Hi,

[#42] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>

32 messages 2002/05/25

[#43] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/26

Hi,

[#44] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/26

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

[#90] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#45] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/26

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

[#46] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/26

Hi,

[#47] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/26

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

[#48] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/26

>>>>> "t" == ts <decoux@moulon.inra.fr> writes:

[#49] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/27

Hi,

[#50] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/27

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

[#51] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/27

Hi,

[#52] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/27

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

[#53] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/27

Hi,

[#54] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/27

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

[#55] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/27

Hi,

[#56] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/27

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

[#57] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/28

Hi,

[#65] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/28

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

[#84] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#92] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/29

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

[#93] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#94] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/29

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

[#95] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#96] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/29

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

[#99] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#100] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/29

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

[#101] RE: possible bug: stack dump with <<-String, #{...} and large loops — "Christoph" <chr_news@...> 2002/05/29

[#103] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/30

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

[#97] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/29

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

[#98] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/29

Hi,

[#181] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/21

Hi,

[#58] Re: possible bug: stack dump with <<-String, #{...} and large loops — matz@... (Yukihiro Matsumoto) 2002/05/28

Hi,

[#59] yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...>

Would it be possible to add '-p ruby' to the bison command line args

8 messages 2002/05/28

[#60] Re: yyparse() and friends >> rubyparse() or rbparse()... — matz@... (Yukihiro Matsumoto) 2002/05/28

Hi,

[#62] Re: yyparse() and friends >> rubyparse() or rbparse()... — nobu.nokada@... 2002/05/28

Hi,

[#61] Re: yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...> 2002/05/28

> |Would it be possible to add '-p ruby' to the bison command line

[#63] Re: yyparse() and friends >> rubyparse() or rbparse()... — matz@... (Yukihiro Matsumoto) 2002/05/28

Hi,

[#64] Re: yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...> 2002/05/28

> |All -p does is add a few #defines for build time at the top of the

[#66] Re: yyparse() and friends >> rubyparse() or rbparse()... — Sean Chittenden <sean@...> 2002/05/28

> > |All -p does is add a few #defines for build time at the top of

[#68] Re: yyparse() and friends >> rubyparse() or rbparse()... — matz@... (Yukihiro Matsumoto) 2002/05/28

Hi,

[#67] The warns-a-thon continues... — Sean Chittenden <sean@...>

I'm feeling left out in this race to clobber warnings!!! Attached are

19 messages 2002/05/28

[#69] Re: The warns-a-thon continues... — matz@... (Yukihiro Matsumoto) 2002/05/28

Hi,

[#88] Re: The warns-a-thon continues... — WATANABE Hirofumi <eban@...> 2002/05/29

Hi,

[#89] Re: The warns-a-thon continues... — matz@... (Yukihiro Matsumoto) 2002/05/29

Hi,

[#91] Re: The warns-a-thon continues... — WATANABE Hirofumi <eban@...> 2002/05/29

Hi,

[#81] Re: The warns-a-thon continues... — Sean Chittenden <sean@...> 2002/05/29

> |*) lots of (a = f()) -> ((a = f())) warns cleanups

[#83] Re: The warns-a-thon continues... — nobu.nokada@... 2002/05/29

Hi,

[#87] Re: The warns-a-thon continues... — Sean Chittenden <sean@...> 2002/05/29

> > > And, why did you include <ctype.h> in util.c?

[#70] Re: The warns-a-thon continues... — WATANABE Hirofumi <eban@...> 2002/05/28

Hi,

[#71] Re: The warns-a-thon continues... — Sean Chittenden <sean@...> 2002/05/28

> :*) Fixed some sprintf() format type mismatches

[#72] Re: The warns-a-thon continues... — Sean Chittenden <sean@...> 2002/05/28

> > :*) Fixed some sprintf() format type mismatches

[#75] Re: The warns-a-thon continues... — nobu.nokada@... 2002/05/28

Hi,

[#82] Re: The warns-a-thon continues... — Sean Chittenden <sean@...> 2002/05/29

> > @@ -408,7 +408,7 @@

[#79] Re: The warns-a-thon continues... — Michal Rokos <m.rokos@...> 2002/05/28

Sean, others,

[#73] Re: The warns-a-thon continues... — ts <decoux@...> 2002/05/28

>>>>> "S" == Sean Chittenden <sean@ruby-lang.org> writes:

[#74] Re: The warns-a-thon continues... — nobu.nokada@... 2002/05/28

Hi,

[#76] Re: The warns-a-thon continues... — WATANABE Hirofumi <eban@...> 2002/05/28

Hi,

[#80] Re: The warns-a-thon continues... — nobu.nokada@... 2002/05/28

Hi,

[#85] Re: The warns-a-thon continues... — matz@... (Yukihiro Matsumoto) 2002/05/29

Hi,

[#77] Long Fmt #2 — Michal Rokos <m.rokos@...>

Hi,

2 messages 2002/05/28

[#78] Re: [Fix] Long Fmt #2 — Michal Rokos <m.rokos@...> 2002/05/28

On Wed, May 29, 2002 at 03:30:07AM +0900, Michal Rokos wrote:

[#86] rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...>

I'm doing a lot of work with Ruby in C and am using some of Ruby's

9 messages 2002/05/29

[#117] Re: rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...> 2002/06/03

At the moment I'm writing an appendix Beginning Ruby Programming

[#119] Re: rb_hash_has_key() and friends non-static... — nobu.nokada@... 2002/06/04

Hi,

[#120] Re: rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...> 2002/06/04

> > As for splitting out the declarations into its own header, that was

[#124] Re: rb_hash_has_key() and friends non-static... — Chris Ross <chris@...> 2002/06/04

[#122] Re: rb_hash_has_key() and friends non-static... — nobu.nokada@... 2002/06/04

Hi,

[#128] Re: rb_hash_has_key() and friends non-static... — Sean Chittenden <sean@...> 2002/06/04

> > > > As for splitting out the declarations into its own header, that was

[#133] Re: rb_hash_has_key() and friends non-static... — nobu.nokada@... 2002/06/05

Hi,

[#118] Re: rb_hash_has_key() and friends non-static... — Joel VanderWerf <vjoel@...> 2002/06/03

Sean Chittenden wrote:

[#102] lib/complex.rb runtime warning... — Sean Chittenden <sean@...>

While using ruby-gnuplot I noticed that lib/complex.rb tosses up a

1 message 2002/05/30

[#104] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...>

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

29 messages 2002/05/30

[#105] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/30

Hi,

[#106] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/31

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

[#112] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/01

Hi,

[#113] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/01

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

[#121] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/04

Hi,

[#123] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/04

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

[#107] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/31

Hi,

[#108] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/31

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

[#109] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/31

Hi,

[#110] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/05/31

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

[#111] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/05/31

Hi,

[#125] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/04

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

[#126] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/04

Hi,

[#127] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/04

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

[#130] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/04

Hi,

[#132] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/05

Hi,

[#134] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/05

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

[#135] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/05

>>>>> "t" == ts <decoux@moulon.inra.fr> writes:

[#137] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/05

>>>>> "t" == ts <decoux@moulon.inra.fr> writes:

[#139] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/05

Hi,

[#141] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/05

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

[#138] Re: possible bug: stack dump with <<-String, #{...} and large loops — matz@... (Yukihiro Matsumoto) 2002/06/05

Hi,

[#142] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/06

Hi,

[#155] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/07

Hi,

[#143] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/06

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

[#147] Re: possible bug: stack dump with <<-String, #{...} and large loops — nobu.nokada@... 2002/06/06

Hi,

[#148] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/06

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

[#140] Re: possible bug: stack dump with <<-String, #{...} and large loops — ts <decoux@...> 2002/06/05

>>>>> "Y" == Yukihiro Matsumoto <matz@ruby-lang.org> writes:

Re: yyparse() and friends >> rubyparse() or rbparse()...

From: Sean Chittenden <sean@...>

Date: 2002-05-28 05:08:27 UTC

List: ruby-core #61

> |Would it be possible to add '-p ruby' to the bison command line
> |args and then change all references from yyparse() to rubyparse()
> |or rbparse()?
> 
> I think plain yacc does not accept '-p'.  Many users compiled Ruby
> using non-bison yacc, so I don't want to force bison to compile.  If
> there's other workaround (probably using cpp), I'd love to merge.

All -p does is add a few #defines for build time at the top of the
generated parser.  I think it would be trivial to duplicate this by
adding this to parse.y.

#define yyparse rubyparse
#define yylex rubylex
#define yyerror rubyerror
#define yylval rubylval
#define yychar rubychar
#define yydebug rubydebug
#define yynerrs rubynerrs

Would this work for you?  -sc

-- 
Sean Chittenden

Thread

In This Thread