[#995] Mathn crashes the interpreter on PPC — Dave Thomas <dave@...>
The following code crashes the interpreter on my Powerbook:
4 messages
2003/05/01
[#1004] irb doesn't work, because tempfile doesn't work — Dave Thomas <dave@...>
Try
7 messages
2003/05/02
[#1005] Re: irb doesn't work, because tempfile doesn't work
— matz@... (Yukihiro Matsumoto)
2003/05/02
Hi,
[#1018] Re: ext/syck problems — why the lucky stiff <ruby-core@...>
U.Nakamura (usa@osb.att.ne.jp) wrote:
8 messages
2003/05/13
[#1037] ping.rb — Dave Thomas <dave@...>
On my Mac OSX,
15 messages
2003/05/14
[#1039] Re: ping.rb
— Ryan Davis <ryand@...>
2003/05/15
[#1040] Re: ping.rb
— Dave Thomas <dave@...>
2003/05/15
Ryan Davis wrote:
[#1042] Re: ping.rb
— nobu.nokada@...
2003/05/15
Hi,
[#1043] Re: ping.rb
— Dave Thomas <dave@...>
2003/05/15
nobu.nokada@softhome.net wrote:
[#1057] Fwd: ping.rb — "J.Herre" <jlst@...>
7 messages
2003/05/16
[#1066] YAML problem — Tanaka Akira <akr@...17n.org>
I found a problem with yaml.
12 messages
2003/05/22
[#1067] Re: YAML problem
— "NAKAMURA, Hiroshi" <nahi@...>
2003/05/22
Hi,
[#1068] Re: YAML problem
— why the lucky stiff <ruby-core@...>
2003/05/22
Concerning error from:
[#1069] Re: YAML problem
— Tanaka Akira <akr@...17n.org>
2003/05/22
In article <20030522064450.GA14175@rysa.inetz.com>,
[#1077] terminated object / invalid inspect_tbl — ts <decoux@...>
10 messages
2003/05/26
[#1078] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1079] Re: [1.8] terminated object / invalid inspect_tbl
— ts <decoux@...>
2003/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#1080] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1081] Re: [1.8] terminated object / invalid inspect_tbl
— ts <decoux@...>
2003/05/26
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
[#1085] Re: [1.8] terminated object / invalid inspect_tbl
— nobu.nokada@...
2003/05/26
Hi,
[#1082] Possible problem with mkmf under Darwin — Dave Thomas <dave@...>
I've been having fun getting readline support to work on OSX. My latest
7 messages
2003/05/26
[#1094] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c — Dave Thomas <dave@...>
> * eval.c (rb_mod_autoload, rb_mod_autoload_p): new method;
12 messages
2003/05/29
[#1095] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— nobu.nokada@...
2003/05/29
Hi,
[#1097] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— Dave Thomas <dave@...>
2003/05/29
nobu.nokada@softhome.net wrote:
[#1101] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— nobu.nokada@...
2003/05/29
Hi,
[#1102] Re: [ruby-cvs] ruby, ruby/lib: * eval.c (ev_const_defined, ev_const_get), variable.c
— matz@... (Yukihiro Matsumoto)
2003/05/30
Hi,
Re: irb doesn't work, because tempfile doesn't work
From:
matz@... (Yukihiro Matsumoto)
Date:
2003-05-02 17:09:18 UTC
List:
ruby-core #1007
Hi,
In message "Re: irb doesn't work, because tempfile doesn't work"
on 03/05/03, Dave Thomas <dave@thomases.com> writes:
|FWIW, I always thought that Object#methods should have accepted a
|'recurse' parameter and that it should have defaulted to 'false'. In
|daily use, I seem to care more about the methods actually defined in an
|object's class than those methods it responds to.
Interesting! As I told you in the personal message, I thought
opposite way. Let me think about this issue more further.
|So, if we're making things incompatible, I'd like to suggest a more
|global change. Make _all_ the reflection methods accept a 'recurse'
|parameter (including things such as method_defined?), and have that
|parameter default to the current 1.6.x behavior. As it stands right now
|we have a curious mixture: some allow you recurse, some let you specify
|it, and some don't recurse.
We both agree to make reflection methods more consistent. I will do
something on it.
|By making the parameter default to the current behavior, we retain
|compatibility for all the developers out there, but by providing the
|parameter we give ourselves future flexibility.
By this way, inconsistency (e.g. instance_methods and methods)
remains. We need to make incompatible change to accomplish
consistency. All is my fault. Sorry.
matz.