Documentation: Difference between revisions

Content added Content deleted
(→‎{{header|MATLAB}} / {{header|Octave}}: Agh. Correct some details.)
Line 697: Line 697:


=={{header|MATLAB}} / {{header|Octave}}==
=={{header|MATLAB}} / {{header|Octave}}==
Script files can contain comments (being whatever follows a % character) and for a script in file Gnash.m that is in the current execute path (so that typing "Fred" will initiate it), the command "help Gnash" will instead display the first comment block. So, if it starts <lang MATLAB>function Gnash(GnashFile); %Convert to a "function". Data is placed in the "global" area.
Script files can contain comments (being whatever follows a % character) and for a script in file Gnash.m that is in the current execute path (so that typing "Gnash" will initiate it), the command "help Gnash" will instead display the first comment block at the start of the file. So, if it starts <lang MATLAB>function Gnash(GnashFile); %Convert to a "function". Data is placed in the "global" area.
% My first MatLab attempt, to swallow data as produced by Gnash's DUMP
% My first MatLab attempt, to swallow data as produced by Gnash's DUMP
%command in a comma-separated format. Such files start with a line</lang>
%command in a comma-separated format. Such files start with a line</lang>
The comments will be revealed. However, a test with Octave elicited only the comment on the "function" line.
The comments will be revealed. However, a test with Octave elicited only the comment on the "function" line. If the file contained merely a sequence of commands (i.e. did not constitute the definition of a function) the first line of the above example would be absent and the file would start with a comment block.


=={{header|Nim}}==
=={{header|Nim}}==