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

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

[Octave-bug-tracker] [bug #48554] doc strings are missing for Octave's .


From: Mike Miller
Subject: [Octave-bug-tracker] [bug #48554] doc strings are missing for Octave's .oct files
Date: Mon, 18 Jul 2016 17:52:27 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0

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

                 Summary: doc strings are missing for Octave's .oct files
                 Project: GNU Octave
            Submitted by: mtmiller
            Submitted on: Mon 18 Jul 2016 10:52:25 AM PDT
                Category: Interpreter
                Severity: 5 - Blocker
                Priority: 5 - Normal
              Item Group: Regression
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Since this change

http://hg.savannah.gnu.org/hgweb/octave/rev/112b20240c87

doc strings for .oct files are no longer accessible.

The quick fix would be to revert that change for the libinterp/dldfcn/*.cc
files.

The built-in-docstrings file that is shipped with Octave contains the doc
strings for _both_ built-in functions and .oct file functions in the dldfcn
directory. However, the install_built_in_docstrings function only loads the
doc string if it's for a built-in.

I don't think changing the function to load doc strings for .oct files will
work, because they are probably cleared when the function is unloaded, for
example with "clear functions".

Since we don't have a solution at the moment for loading comment-based doc
strings from compiled .oct files, I think we should just change those files
back to using strings compiled in to the object code.




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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