[#5563] Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...>

Lately, I've been thinking about the future of ruby

44 messages 2005/08/19
[#5564] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/19

On 8/19/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:

[#5571] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/19

--- Austin Ziegler <halostatue@gmail.com> wrote:

[#5574] Re: Non-overridable and non-redefinable methods — TRANS <transfire@...> 2005/08/20

Just wanted to add a few things.

[#5581] Re: Non-overridable and non-redefinable methods — Austin Ziegler <halostatue@...> 2005/08/20

On 8/19/05, TRANS <transfire@gmail.com> wrote:

[#5583] Re: Non-overridable and non-redefinable methods — "David A. Black" <dblack@...> 2005/08/20

Hi --

[#5585] Re: Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...> 2005/08/20

--- "David A. Black" <dblack@wobblini.net> wrote:

[#5609] Pathname#walk for traversing path nodes (patch) — ES <ruby-ml@...>

Here is a small addition to Pathname against 1.9, probably suited

20 messages 2005/08/22

Re: uri test failures. (Re: [ruby-cvs] ruby/lib, ruby/lib/uri: Lovely RDOC patches from mathew (metaATpoboxDOTcom) on URI/* and getoptlong.rb)

From: "Warren Brown" <warrenbrown@...>
Date: 2005-08-26 19:09:17 UTC
List: ruby-core #5691
mathew,

> As documented in RFC 1738 section 3.2.2 (and now
> documented in the classes too),
> ftp://ftp.example.com/foo/bar/file.ext should parse
> into a server of ftp.example.com, and a path of
> foo/bar/file.ext with no leading slash.
>
> If you want a leading slash on your chdir command,
> you need to escape it in the URL, e.g.
> ftp://ftp.example.com/%2Ffoo/bar/file.ext.

    As I pointed out in
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/5285 (the
last time this issue came up), RFC1738 was updated by RFC1808 and
RFC2396 to include FTP URLs under the URI "umbrella".  This means that
although the second slash *is* required for absolute paths, it is *not*
required to be encoded as "%2F", it can just be a regular slash ("/").
So the second paragraph above should read "If you want a leading slash
on your chdir command, you need to insert a second slash (e.g.
'ftp://ftp.example.com//foo/bar/file.ext')."

    Hopefully the patched code allows this as well.

    - Warren Brown




In This Thread

Prev Next