lør, 05 09 2009 kl. 16:36 +0200, skrev Javier Enciso:
> Yes, It does. Although a new question emerges...
>
> Consider, for example, the definition of the 'warranty' help string
> given by the octave-3.2.2/src/DOCSTRINGS file, say,
> warranty
> @c toplev.cc
> -*- texinfo -*-
> @deftypefn {Built-in Function} {} warranty ()
> Describe the conditions for copying and distributing Octave.
> @end deftypefn
>
> out of this definition, and after execute the admin/split_docstrings
> script, a new file called 'warranty' will be created, replacing the old
> one, at octave-forge/language/base/help/octave/ with the following
> content:
> @c toplev.cc
> -*- texinfo -*-
> @deftypefn {Built-in Function} {} warranty ()
> Describe the conditions for copying and distributing Octave.
> @end deftypefn
>
> So far, the files located at octave-forge/language/base/help/octave/
> start omit the line "@c toplev.cc", instead they start with "-*- texinfo
> -*-", so the question is, is that behavior intended?
Sorry, but I don't know :-(
Does anybody else know? Otherwise, I'm afraid you'll have to investigate
this one yourself :-(
Søren
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
