[#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

File.extname edge case bug?

From: Daniel Berger <Daniel.Berger@...>
Date: 2005-08-23 17:24:17 UTC
List: ruby-core #5651
Hi all,

Ruby 1.8.2
Solaris 10

Should File.extname("..") return "" or "."?  It currently returns ".".

The comments in the source say that it returns an empty string if the 
string provided as an argument begins with a "." and is the only "." in 
the string.

I would argue that any string that begins with a ".", regardless of how 
many total "." there are in the string, should return an empty string. 
My opinion is based on years of convention.  I have never, ever seen 
string that began with "." and had an extension as well.  No one ever 
does this afaik.

Am I wrong?  Thoughts?

Regards,

Dan

In This Thread

Prev Next