[#3479] Missing .document files for ext/ libraries — Brian Candler <B.Candler@...>
The ri documentation for zlib, strscan and iconv doesn't get built by 'make
On Wednesday, October 6, 2004, 11:18:33 PM, Brian wrote:
Just been building CVS head and was surprised at how long it now takes
On Die, 2004-10-19 at 16:47, Dave Thomas wrote:
[#3484] compilation error — Wybo Dekker <wybo@...>
In the current cvs I get, on make:
On Mon, Oct 11, 2004 at 07:21:28AM +0900, Wybo Dekker wrote:
[#3486] Location of missing end — Markus <markus@...>
Over the past week or so there has been a thread on ruby-talk ("Quality
[#3492] Re: ANN: Free-form-operators patch — Markus <markus@...>
> In message "Re: ANN: Free-form-operators patch"
Hi,
On Mon, 2004-10-11 at 16:16, Yukihiro Matsumoto wrote:
On Monday 11 October 2004 08:09 pm, Markus wrote:
Hi,
On Monday 11 October 2004 09:38 pm, Yukihiro Matsumoto wrote:
[#3517] Kernighan & Richie ---> prototypes ? — Johan Holmberg <holmberg@...>
[#3523] segfault in ruby-1.8.2p2 — Brian Candler <B.Candler@...>
I can reliably get ruby-1.8.2p2 to segfault on my system, which is:
[#3538] TCPSocket.new(host, port).readline hangs on Windows — Jos Backus <jos@...>
With recent CVS versions (both ruby_1_8 branch and HEAD), the following
Hi,
On Wed, Oct 20, 2004 at 07:43:31AM +0900, Yukihiro Matsumoto wrote:
[#3551] ubygems missing? — "trans. (T. Onoma)" <transami@...>
I've never been one for compiling code, so I bet this is a simple fix, but
[#3561] 1.8.2 - what can we do to help? — Dave Thomas <dave@...>
Folks:
Hi,
On Oct 26, 2004, at 9:55 PM, Yukihiro Matsumoto wrote:
On Wed, 2004-10-27 at 06:11, Francis Hwang wrote:
On Wed, 27 Oct 2004, Yukihiro Matsumoto wrote:
Hi,
On Wed, 27 Oct 2004, Yukihiro Matsumoto wrote:
Hi,
On Wednesday 27 October 2004 08:51 am, Yukihiro Matsumoto wrote:
[#3573] Small issues with Symbols — Florian Gro<florgro@...>
Moin!
[#3590] Re: Bug tracking project on RubyForge... — "Berger, Daniel" <Daniel.Berger@...>
> -----Original Message-----
Sure...
Hi,
[#3596] Float and Bignum — "trans. (T. Onoma)" <transami@...>
Hi all,
Hi,
On Thursday 28 October 2004 02:00 am, Yukihiro Matsumoto wrote:
[#3600] Ruby Vs. ... might find comparison of interest. — "trans. (T. Onoma)" <transami@...>
trans. (T. Onoma) wrote:
[#3610] Tadayoshi Funaba's Date2 — "trans. (T. Onoma)" <transami@...>
Tadayoshi Funaba has a lib on RAA called Date2, the additions/improvements to
Hi --
On Friday 29 October 2004 07:03 am, David A. Black wrote:
[#3611] Memory leak in ruby_1_8 — David Ross <dross@...>
Hello,
[#3617] TEST BUG — noreply@...
Bugs item #1000, was opened at 2004-10-28 09:12
[#3638] Ruby, pthreads, and HPUX 11 — Jamis Buck <jgb3@...>
I'm finally trying to delve into the issue of Ruby not compiling
>>>>> "J" == Jamis Buck <jgb3@email.byu.edu> writes:
[#3655] autoload — Joel VanderWerf <vjoel@...>
Re: 1.8.2 - what can we do to help?
On Wednesday, October 27, 2004, 11:11:49 PM, Francis wrote: > [...] > Am I totally off-base here? Slightly. My perspective is that ruby-core is a perfectly suitable place to bring up issues in the standard library. The code might have a single author, but being distributed with Ruby, it has many de facto maintainers. Patches can be proposed, and I doubt Matz would hesitate to commit them if the original author can't be contacted. That's my opinion, not necessarily existing policy. Standard of documentation is a separate, but obviously important matter. Matz has said on -core that any future additions to stdlib must be well documented. The question of where bug reports go is often asked, yet to me it's obvious: ruby-core (or ruby-talk if the finder is not subscribed to -core). It's better than sending them nowhere; it's better to bring them to wide attention, not just the original author. And someone will pipe up and tell you if they should go somewhere else. But even if/when we use a RubyForge project to track bugs, they will never be off-topic on -talk or -core, and it may be better to discuss a bug before tracking it. Perhaps I'm off-base here, but I guess it would help to work out real answers to these questions and stick them in the FAQ, and on a bug-reporting section of ruby-lang. Cheers, Gavin