From: "H.Yamamoto" <ocean@...2.ccsnet.ne.jp>
Date: 2004-02-23T13:23:50+09:00
Subject: File.fnmatch's behavior

Hi, rubyists.

I'm now thinking of File.fnmatch's behavior.
I've read [ruby-dev:16555] and agreed the point

  "It sounds good to me that FNM_PATHNAME behavior is default (and introduce oposite flag like FNM_SLASHMATCH),
   and '**/' is implemented."

Is this change acceptable?

And current bracket expression's behavior is similer to ruby's regular expression and differs from SUSv3.

  Current:
    File.fnmatch("[a/c]", "a", FNM_PATHNAME) # => true (ignore '/' in bracket expression)
    File.fnmatch("[\\*]", "\\") # => false (\ is escaping character)
    File.fnmatch("[\\*]", "*") # => true

  SUSv3:
    File.fnmatch("[a/c]", "a", FNM_PATHNAME) # => false ('/' has supiority over bracket expression)
    File.fnmatch("[a/c]", "[a/c]", FNM_PATHNAME) # => true (so, '[a' is handled like ordinary character)
    File.fnmatch("[\\*]", "\\") # => true (\ is ordinary character)
    File.fnmatch("[\\*]", "*") # => true

Which one is prefered?

Any comments will be appreciated.

Regards,

Yamamoto.