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

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

[Octave-bug-tracker] [bug #47299] lookfor without doc-cache extremely sl


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #47299] lookfor without doc-cache extremely slow, many warnings
Date: Sun, 28 Feb 2016 19:41:31 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Iceweasel/44.0.2

URL:
  <http://savannah.gnu.org/bugs/?47299>

                 Summary: lookfor without doc-cache extremely slow, many
warnings
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Sun 28 Feb 2016 11:41:29 AM PST
                Category: Octave Function
                Severity: 1 - Wish
                Priority: 5 - Normal
              Item Group: Performance
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

The lookfor function normally relies on the doc-cache file that contains an
index of all function docstrings.

When Octave is built with --disable-docs, the doc-cache file is not built and
the lookfor function falls back to pulling the docstrings straight out of
every function in the symbol table.

I just tested this and it is extremely slow (understandable for what it's
doing), and produces a lot of the following warning messages:


warning: concatenation of different character string types may have unintended
consequences
warning: Octave language extension used: OP used as operator near ...
warning: Octave language extension used: bare newline inside parentheses near
...


I'm not at all sure at the moment what's causing these warnings, but it would
probably be useful to improve the experience for people who rely on lookfor
since there are screenfuls of these warning messages before any useful output
is shown.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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