[#686] Wall compilation — Michal Rokos <michal@...>
Hi everybody,
[#688] mkmf.rb - add files to clean and distclean targets — Michal Rokos <michal@...>
Hi,
On Thu, 16 Jan 2003, Michal Rokos wrote:
Hi,
Hi,
On Tue, Jan 21, 2003 at 11:16:39AM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 06:38:00PM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 11:37:35PM +0900, Yukihiro Matsumoto wrote:
Hi,
Hello,
Hi,
Hi,
Hi,
Hi,
[#708] Documentation for thread.rb — Gavin Sinclair <gsinclair@...>
Hi ruby-core,
[#719] nd_end and NODE_NEWLINE (fwd) — Chad Fowler <chad@...>
[#724] Symbols: More Functionality Wanted — Ryan Pavlik <rpav@...>
I've been discussing this for a bit on #ruby-lang on OPN (or freenode or
Hi,
On 20 Jan 2003 at 15:49, Yukihiro Matsumoto wrote:
Hi --
On Thursday, January 23, 2003, 6:28:04 AM, dblack wrote:
Gavin Sinclair <gsinclair@soyabean.com.au> writes:
Hi,
matz@ruby-lang.org (Yukihiro Matsumoto) writes:
Hi,
On Fri, 24 Jan 2003 03:34:46 +0900
[#730] Comments on matrix.rb — Gavin Sinclair <gsinclair@...>
Hi -core,
[#757] Extensions for Time and ParseDate — Ryan Davis <ryand-ruby@...>
Eric and I have been hacking around and we can't stand the lack of
[#759] Adding Test::Unit to CVS — "Nathaniel Talbott" <nathaniel@...>
Matz has already given me the go-ahead to add Test::Unit to CVS, but I
Nathaniel Talbott wrote:
On Wednesday, January 22, 2003, at 07:56 AM, Dave Thomas wrote:
Re: Documentation for thread.rb
On Friday, January 17, 2003, 12:45:30 PM, Yukihiro wrote: > | I include page references, because they are currently in ri. > This should eventually removed. OK, I'll leave them in for now, for consistency, and to avoid wasting too much time thinking about it. > | I don't include class examples from the Pickaxe, but should I? > Perhaps. I'll try, and see how it comes out in HTML. > |Note especially that Queue and SizedQueue are not documented in > |Pickaxe (online version). At least I can't find them. I've therefore > |made a comment in the code asking if "Ruby in a Nutshell" should be > |used as a source instead. > Please. You can use the Nutshell Thanks. I'll do that before committing. > |[1] I'm inexperienced in creating patches - I just used cvs diff -u. > |I don't expect this to be treated as a patch just yet anyway. > This is excellent. And you can commit them. Now you are the > committer, aren't you? I am. So, just to confirm: the committed code may have things like "FIXME" etc. I think that's OK, but someone needs to make sure these are resolved or removed before the next release. I am happy to be given the task of reviewing all RDoc in CVS when the time comes. Should I post here again before committing this file? What about other files? Gavin