octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #60157] save() expressive filtering when using


From: N Kando
Subject: [Octave-bug-tracker] [bug #60157] save() expressive filtering when using brackets [ ] does not appear to work.
Date: Tue, 2 Mar 2021 17:08:46 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36

Follow-up Comment #2, bug #60157 (project octave):

But the documentation never even mentions regular expressions. 

Only from familiarity with matlab's save('-regexp') option did I associate
regular expressions with octave's save() function. I thought octave's save()
function might only have tools which offer a limited set of commands which
parallel regexp, because the documentation is unclear unless (or even if) the
user has prior knowledge.

I had also looked up LIST to see if there was any common usage detailing the
syntax of what could be input, but there's no identifying words of what could
go here.

Here's the whole section:


     The list of variables to save may use wildcard patterns containing
     the following special characters:

     '?'
          Match any single character.

     '*'
          Match zero or more characters.

     '[ LIST ]'
          Match the list of characters specified by LIST.  If the first
          character is '!' or '^', match all characters except those
          specified by LIST.  For example, the pattern '[a-zA-Z]' will
          match all lower and uppercase alphabetic characters.

          Wildcards may also be used in the field name specifications
          when using the '-struct' modifier (but not in the struct name
          itself).



"The list of variables to save may use wildcard patterns containing the
following special characters" makes it sound like the options provided are an
exhaustive list.

If regular expressions can be used to refer to anything in the workspace, I
believe the documentation should be edited to make that clear and to suggest
the user review the regexp() command for more information.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?60157>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]