[ruby-talk:02587] Re: Replies for

From: matz@... (Yukihiro Matsumoto)
Date: 2000-04-27 03:21:51 UTC
List: ruby-talk #2587
Hi,

In message "[ruby-talk:02583] Replies for"
    on 00/04/27, mrilu <mrilu@ale.cx> writes:

|I wonder why my earlier message was avoided. Answers to this help me to
|write better in the future.

Sorry, it was just in the middle of my 2 week off from office.  I put
your mail in the ToDo queue, then forgot it.  Terribly sorry.

|I'm still waiting replies for my message [ruby-talk:02339] regarding
|following topics:
|- description of differences and uses for irb, eval and debug

 irb - interactive ruby.
 eval.rb - ditto.  obsoleted by irb.
 debug.rb - ruby debugger.  input must be fit in a line.

|- patching policy: mail to list, to matz or direct cvs (possible?)
|  - if mailing should patch be in body or as attachment

Mailing a patch to this list is preferable for me, if it isn't too big
(i.e. less than 200 lines).  Some trusted contributors have their
account for the CVS repository.

|- few questions regarding unclear debug functionality

In message "[ruby-talk:02339] Patch: Debugger help"
    on 00/04/02, mrilu <mrilu@ale.cx> writes:

>+  b[reak] [filename:]<line>  set breakpoint to some position
>+    I'm a little bit unsure here. break doesn't seem to use filename.

Enther filename or method name is OK for the prefix.

>+  m[ethod] i[nstance] <obj>  show object's methods
>+  m[ethod] <obj>             show object's instance methods
>+    Should these method listings be in other order?

+  m[ethod] i[nstance] <obj>  show object's methods
+  m[ethod] <obj>             show instance methods of class or module

>+  th[read] c[ur[rent]]       list current threads
>+    Stopped threads?
>
>Bad name, IMO, if this lists stopped threads. 'Current' is already 
>overloaded in stopping threads.

It shows the current thread information.  Current would not be
overridden since no context switch would happen in the debugger.

|- help language issues
|
|Maybe there should be some common i18 or localization policy in Ruby, so
|that it would ship with at least English and Japanese helps built-in.

English is OK for me.  I18N effort will be done someday.
Their's only one I18N policy for Ruby.

  It should not cause me trouble handling Japanese.

How poor it is.  I'm still surveying real I18N stuff.

							matz.

In This Thread

Prev Next