|
From: | Rik |
Subject: | Re: inputParser documentation |
Date: | Wed, 18 Mar 2015 11:08:22 -0700 |
On 03/18/2015 09:00 AM,
address@hidden wrote:
I wonder if this is also related to the behavior of which()? octave:1> which inputParser 'inputParser' is a built-in function octave:2> which sin 'sin' is a built-in function from the file libinterp/corefcn/mappers.cc octave:3> which inputParser.m 'inputParser.m' is the file /home/rik/wip/Projects_Mine/octave-dev/scripts/general/inputParser.m octave:4> which sind 'sind' is a function from the file /home/rik/wip/Projects_Mine/octave-dev/scripts/elfun/sind.m The first line does not look correct.
I don't think we have a solution yet for classdef files and documentation. Previously, every m-file had a single texinfo block at the top that was parsed. If you were using the old class syntax, then every method was also it's own m-file in a @classname directory. This is how the @ftp class works and if you look at system.txi there is a DOCSTRING entry for each m-file. We might not figure a solution to this before the 4.0 release. --Rik |
[Prev in Thread] | Current Thread | [Next in Thread] |