[#5143] Win32API segfault in 1.8.3p1 — Nathaniel Talbott <ntalbott@...>
I'm on Windows XP, using VC7 to compile. I've previously gotten a good
Hi,
[#5151] COPY and INSTALL on Windows — Nathaniel Talbott <ntalbott@...>
1.8.3p1 has changed the defaults for the COPY and INSTALL Makefile
[#5152] 1.8.3 p1 segfault in array.c- bccwin32 - bcc5.5 (free) compiler bug — "daz" <dooby@...10.karoo.co.uk>
[#5160] Alternative for win32\ifchange.bat — "daz" <dooby@...10.karoo.co.uk>
[#5179] Cannot build HEAD on OS X 10.4.1 — Eric Hodel <drbrain@...7.net>
Somehow the rb_fd_init macro is conflicting with the definition of
Hi,
Hi,
[#5188] Re: IO#read — Yukihiro Matsumoto <matz@...>
Hi,
[#5190] Resolv and TTL — Eric Hodel <drbrain@...7.net>
I would like to retrieve the TTL values from Resolv, but they seem to
[#5206] Object#inspect() doesn't return; uses 100% cpu — Andrew Walrond <andrew@...>
Is this something I could have caused by overriding some method on the
[#5211] ruby 1.8 CVS do not work with --enable-pthread configure option — noreply@...
Bugs item #2038, was opened at 2005-06-16 13:57
[#5215] Hackers Guide Translation Request! — "Charles E. Thornton" <ruby-core@...>
I have recently discovered RUBY and want to understand it a deep level -
[#5219] Segmentation fault in timeout.rb — Michel Pastor <K@...>
Hi,
On Fri, 17 Jun 2005 05:03:18 +0900
Hi,
On Fri, 17 Jun 2005 11:51:07 +0900
Hi,
On Sat, 18 Jun 2005 10:28:53 +0900
Hi,
On Sun, 19 Jun 2005 23:05:56 +0900
[#5233] event_hook shows weirdness when invoked on mixed in methods — Ryan Davis <ryand-ruby@...>
The following attachment, when run, shows the following behavior:
[#5264] XMLRPC vulnerabilities? — Hugh Sasse <hgs@...>
I've just seen this (by RSS)
[#5267] RubyUnit Test Ordering — Jordan Gilliland <jordan@...>
I'm using ruby 1.8.2 (2004-12-25) [i686-linux] and I've noticed that the
[#5277] Macros in win32.h — james@...
win32.h defines a load of macros. This means any C or C++ program which embeds
[#5288] committing rdoc additions corrections to head? — Ryan Davis <ryand-ruby@...>
There is some discussion on ruby-doc about people documenting core
[#5296] Subversion — Shugo Maeda <shugo@...>
Hi,
Shugo Maeda wrote:
Curt Hibbs wrote:
On 6/30/05, Nikolai Weibull
Austin Ziegler wrote:
On 6/30/05, Nikolai Weibull
Austin Ziegler wrote:
On 6/30/05, mathew <meta@pobox.com> wrote:
Austin Ziegler wrote:
On 7/1/05, mathew <meta@pobox.com> wrote:
Austin Ziegler wrote:
On 7/1/05, Nikolai Weibull
Austin Ziegler wrote:
On 7/1/05, mathew <meta@pobox.com> wrote:
Austin Ziegler wrote:
On Thursday 30 June 2005 19:19, mathew wrote:
"Sean E. Russell" <ser@germane-software.com> writes:
On 30 Jun 2005, at 08:19, Shugo Maeda wrote:
Hi,
[ ruby-Bugs-2055 ] URI::FTP handles path incorrectly as per RFC 1738
Bugs item #2055, was opened at 2005-06-24 18:03
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=2055&group_id=426
Category: Standard Library
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: mathew ! (meta)
Assigned to: Nobody (None)
Summary: URI::FTP handles path incorrectly as per RFC 1738
Initial Comment:
RFC 1738 specifically states that the path for an FTP URI does not include the / which separates the URI path from the URI host. Example:
ftp://ftp.example.com/pub/ruby
The above URI indicates that the client should connect to ftp.example.com then cd pub/ruby from the initial login directory, *not* cd /pub/ruby.
Similarly, for an absolute FTP path such as cd /foo/bar, the leading / must be escaped as %2F.
In other words, FTP URIs are interpreted differently from generic URIs (RFC2396). Currently the standard library treats them the same as generic URIs, so the path returned from parsing an FTP URI is wrong, and valid paths passed to build() result in errors.
I've fixed the standard library code to adhere to RFC1738 for FTP URIs, and also improved the documentation. I can provide diffs from the CVS sources, and I'll upload the fixed lib/uri/ftp.rb.
I've got extra documentation for the rest of the URI library too, but I'm not sure where to upload it to?
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=2055&group_id=426