[Octave-bug-tracker] [bug #47950] glob and dir functions are unable to escape square bracket characters in Windows

[Mike Miller]

Follow-up Comment #24, bug #47950 (project octave):

Discussion with jwe on #octave about this bug resulted in us thinking we
should *not* introduce more system-dependent functionality, and instead make
the dir() function behave differently from the glob() function, regardless of
the OS. I think the core problem, that dir() should work the same as the DOS
command DIR, is addressed either way, but this way avoids the risk of
accidentally introducing some inadvertent system-dependent behavior because of
some other function or script using dir() or glob() in an unanticipated way.

So our thinking is to either introduce a new function that is similar to glob
but only allows the asterisk and question mark wildcard characters to be
passed down to the real glob C function, or to add an option that does the
same such that it is only called from dir.m to do DOS/Windows-style
wildcards.

This means the dir() function will behave the same on Unixy operating systems
as well, and its documented wildcard matching behavior will be different from
the glob() and ls() functions.

So I think the first step would be either duplicating octave::sys::glob or
adding an optional parameter that changes its behavior as described and
exposing that such that it can be called that way by dir.m.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47950>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/