[#192] auto-loaded script? — Julian Fondren <julian@...>
Does ruby load any particular scripts upon startup?
13 messages
1999/01/17
[#193] Re: auto-loaded script?
— gotoken@... (GOTO Kentaro)
1999/01/17
In message "[ruby-talk:00192] auto-loaded script?"
[#194] Re: auto-loaded script?
— Julian Fondren <julian@...>
1999/01/18
> >Does ruby load any particular scripts upon startup?
[#195] Re: auto-loaded script?
— matz@... (Yukihiro Matsumoto)
1999/01/18
Hi.
[#197] Re: auto-loaded script?
— Julian Fondren <julian@...>
1999/01/18
> rb_load_file("/home/julian/.rubyrc"); /* this line added */
[#210] Get character with no wait — Gabriel <gabriel@...>
What is the best way to do a getc without waiting; so I can try to grab
8 messages
1999/01/25
[ruby-talk:00191] defining self causes a segmentation fault
From:
Julian Fondren <julian@...>
Date:
1999-01-17 05:11:11 UTC
List:
ruby-talk #191
Hello,
In ruby you can't change the value of self, and I just learned this,
because of the following:
ruby0> def ls(self='.')
ruby1> print `gnuls --color -aFx #{self}`
ruby1> end
(eval):0: [BUG] Segmentation fault
Of course the above doesn't really explain what the problem was, but I
experimented some more and found that even this:
ruby0> self=nil
will - also when defining it to 0, or 'some string', result in this:
(eval):0: [BUG] Segmentation fault
And then in the drawing up of this email I found:
$ ruby
self=nil
-:1: Can't change the value of self
self=nil
^
-:1: [BUG] Segmentation fault
which partially explains things. I assume here that this is some kind of
bug and that ruby isn't supposed to segfault on an attempt to define
self.. though maybe it is. Also this might be restricted to my machine -
something I have certainly seen before - or at least the segfault part
might. Anyway, what's the deal here?
thanks,