[Octave-bug-tracker] [bug #47820] Uncomprehesive behaviors for functions that are not recognized in configure

[Lachlan Andrew]

Follow-up Comment #1, bug #47820 (project octave):

Is the problem here that the documentation doesn't match the actual
functionality, or is it just that you want the missing functionality to be
implemented?

If it is the documentation issue, that is related to bug #36524.  At the
moment, the documentation can only be a single string.  Having
configuration-dependent strings requires the entire string to be repeated
(with appropriate modifications) in #ifdef statements.

I would like there to be a system that allows #ifdefs within the string -- for
example, allowing the fork documentation to mention that it is not available
on the current system, and possibly saying what configuration changes are
required to enable it.

Of course, that doesn't get any closer to actually implementing it...

    _______________________________________________________

Reply to this item at:

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

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