From: Teddy on
Hi,

I would like to create my own toolbox by gathering and cleaning my previous pieces of code (which were quickly and dirty implemented). Is there any guidelines document detailing how to write as proper as possible matlab codes, how to organize things in a toolbox, how to document codes etc.

Thanks for your help.

Teddy
From: per isakson on
"Teddy " <teddy.furon(a)inria.fr.remove.this> wrote in message <i26gfg$l56$1(a)fred.mathworks.com>...
> Hi,
>
> I would like to create my own toolbox by gathering and cleaning my previous pieces of code (which were quickly and dirty implemented). Is there any guidelines document detailing how to write as proper as possible matlab codes, how to organize things in a toolbox, how to document codes etc.
>
> Thanks for your help.
>
> Teddy

1. "The first comment line (the H1 line) of the help text in all MATLAB program files" is important ... as is the help section of each function

2. http://www.datatool.com/downloads/matlab_style_guidelines.pdf

3. http://www.artefact.tk/software/matlab/m2html/

4. http://www.advancedmcode.org/debugging-profiling-style-guidelines-in-matlab.html

5. Matlab's function, PUBLISH.

6. There are a lot of code to inspect and learn fron in Matab itself and the File Exchange (filter needed) and ...

I don't know of any The Guide, however, much of what applies with other languages applies to Matlab.

/ per