How do you include authorship and version info into your MATLAB functions [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 5 years ago.

Improve this question

This question is related to my previous one: MATLAB m-file help formatting.

What do you usually write to describe authorship of your own function? Do you put it at the end of the function body or right after the help text before any code?

How do you include version information? Is it possible to automat开发者_开发知识库ically update version after function modification?

This is what I usually include:

% My Name <my@email>
% My company
% Created: September 2010
% Modified: October 2010

Please share your thoughts, ideas?

---

I have a function in the MATLAB Central File Exchange that helps you document your function in a standard way, and works with version control software (CVS and Subversion; not git) to automatically update the author field and time of modification.

You just type new at the command prompt, then the name of the function, and it sorts out the rest.

The basic template for documentation that I use is

function [outputArgs] = TestFunction(inputArgs)
%TESTFUNCTION Summary of this function goes here
% 
% [OUTPUTARGS] = TESTFUNCTION(INPUTARGS) Explain usage here
% 
% Examples: 
% 
% Provide sample usage code here
% 
% See also: List related files here

% $Author: rcotton $    $Date: 2010/10/01 18:23:52 $    $Revision: 0.1 $
% Copyright: Health and Safety Laboratory 2010

(You'll obviously want a different company in your copyright statement.)

The first line of the help documentation is known as the H1 line, and is used by the function lookfor, among others. It is important that this comes straight after the function definition line.

If you have different use cases (maybe with and without optional arguments), then you should describe each one.

The Examples: and See also: lines are formatted in a way the works with the help report generator. (I've just spotted a bug - the year should be before the company name in the copyright line. Fix on its way.)

$Author:, etc., are formatted for use with CSV/SVN. Since git uses hashes of files, you can't change the content of the file, without git thinking that it's been updated.

---

We keep our code in a Subversion repository and use the keywords functionality for writing this sort of information into the header comments of the m-file when it is committed to the repo. We put a block of comments right after the initial function line in (most of) our m-files.

If you are not using a source code control system then:

1. You really should start using one right now.
2. You could write a script (in Matlab, why not) for maintaining the comment information you require, and implement some process to ensure that you run the script when necessary.

We don't generally put modification dates or histories in our source files, the repository tracks changes for us. Which is another reason you should be using one.

And, while you are thinking about all this, if you haven't already done so: check out Matlab's publish functionality.

EDIT: @yuk: I guess from your mention of TortoiseSVN that you are working on Windows. It's a couple of years since I installed Subversion on my Windows PC. I don't recall any problems at all with the installation, and I'm not qualified to help you debug yours -- but there are plenty on SO who are.

As for keeping version (etc) info up to date, there's no scripting required. You simply include the special strings, such as $Rev$, which Subversion recognises as keywords in the locations in your files (probably in the comments) where you want the version information (etc). This is well explained in the Subversion Book.

As for the Matlab documentation, I think the publish (and related) features are well explained in the Desktop Tools and Development Environment handbook which is available on-line at the Mathworks web-site.

---

As High Performance Mark points out, some form of source code control is ideal for handling this situation. However, if you are adding information by hand here are a few pointers:

• I would definitely include a line stating the MATLAB version your code was written in, or perhaps which versions you know it works for.

• When adding the information, you have to leave space between it and the help comment block if you don't want to display it when the user views the help contents, like so:

  function myFunction
  %# Help text for function
  
  %# Your information
  

  Unless you do want it displayed with the help. Then just make one big comment block.