MATLAB Programming Style Guidelines

13 pages of advice on writing clear code.

Description

Advice on writing MATLAB code usually addresses efficiency concerns, with recommendations such as "Don't use loops." This document is different. Its concerns are correctness, clarity and generality. The goal of these guidelines is to help produce code that is more likely to be correct, understandable, sharable and maintainable.

This document lists MATLAB coding recommendations consistent with best practices in the software development community. These guidelines are generally the same as those for C, C++ and Java, with modifications for MATLAB features and history. The recommendations are based on guidelines for other languages collected from a number of sources and on personal experience.

This file is also available at http://www.datatool.com/prod02.htm

• MATLAB release: MATLAB 6.5 (R13)

[Matthew Simoneau]

Great work. The document is well-written and spot-on. A much-needed addition to the MATLAB community.

[Penny Anderson]

I thought this document encapsulated a boat load of good advice relevant for many programming languages, and included some nice MATLAB specific hints.

Detailed comments:
Longer, more descriptive variable, function and file names are good, except when math training takes over. I am never going to refer to A, x and b in the system of linear equations A*x=b by any other names ;-)

My exception to the rule about iterators being in alphabetical order is when using them to access entries in an array (granted, we try to discourage this behavior in the first place, but it's not always feasible). In this case, I generally use i for rows, j for columns and k for pages if it's a 3D array, regardless of the loop order. For more dimensions I would use something like i1,i2,i3, ...

In the section on Conditionals, I would replace "Complex" with "Complicated" to avoid confusion with MATLAB's complex numbers.

[daniel he]

 

[nandha kumar]

good

[Predrag Kovacevic]

 

[eduardo perez]

 

[Tanveer Yasser]

 

[Lei Wang]

Good convention for programming large codes

[Matlab User]

Most parts are borrowed from other languages. Can't see much useful information.

[B G]

Very helpful. I typically write in MATLAB, and I haven't read about style guidelines before. This will help me write more readable and more maintainable MATLAB code.

[a l]

 

[another user]

Opinionated, but well thought out for issues specific to Matlab :-). I liked it! I wonder if something like this exists for Simulink as well?

[Angelo Stranieri]

Cannot download PDF. Acrobat 5.0 says there is an error in the file.

[Cristian Gutiérrez]

Very instructive this material. However, requires knowing about Matlab programming.

[vikas jain]

thanks for such facility.

[John Bucsek]

No problems viewing file. A good collection of programming tips.

[Dr K. Olp]

Generally, most of this should already be known and adhered to by any professional programmer, however it is sometimes useful to have it 'written down' as a reference. Useful as a beginners guide.

[Viet Tung NGUYEN]

 

[Alexander Toniatti]

 

[Adam Remy]

 

[James Cline]

Concise, good examples

[Tom Alen]

 

[ramin vasfpour]

 

[kikaw wahyudi]

 

[old programmer]

no news

[Dennis James]

Standards are always welcome in structured programming. This is an attempt at standardizing.

[hamid reza mohammadi]

 

[Anatoly Shadrin]

 

[John Solar]

Very good. But a little too kind. Mandate instead of suggest! Also, i and j should never be used. Code may get expanded to use complex numbers. It is also a bad habit that might allow a slip in the future. You are not doing favors by allowing it sometimes.

[sudharsan kannan]

 

[w j]

good

[Bharani Krishnamurthy]

very good

[Fahad Al Mahmood]

Great & Appreciated Guidelines!
I hope I can follow all of them!

[Michael Villalba]

An excellent collection, great for beginning or intermediate Matlab coders.

[Saeed Attarzadeh]

It's great

[nhgg jhgu]

 

[shivanand b]

 

[nigus Habtu]

I am greatful to Matlab& I am very happy if give me this documment.

[Mark Newton]

Useful, short document that reminds one of all the things they should already do, but probably don't.

[William Zimmerman]

Concise and thorough

[aki arso]

ok

[takis soteropoulos]

 

[Gavril Grebenisan]

The file is damaged and I cannot open

[skr sleem]

 

[Fa Esu]

Your documemet is not structured enough yet. Try use a standard LaTex. More examples could be helpful and thus self-explanatory. Thanks, btw.

[H Patel]

File is damaged and I couldn't open it.

[muthu kumar]

i am very greatful

[- -]

 

[Marcio Andre Andre]

  Gostei muito me ajuda guando trabalho com matrizes ele é otimo se duvidas...
 MARCIO ANDRE /// FLORIANÓPOLIS SC
                BRASIL

[James Bonanno]

 

[Richard Kirkeeide]

Clear, concise and reasonable. Should be alot of help to me (and others). Thanks

[John Solar]

 

[Fu-Sung Wang]

After I read this article, I'm impressed some good stuffs that I uesed to ignore or misuderstand. This pdf file is easy understood and it's especially useful for MATLAB experienced programmers. The guidelines helped me to construct a more standardized, easy-maintained programs. No matter what kind of languages you are using, there will be some concepts you can refer to.

[Rene Just Nielsen]

 

[Frederic Bosche]

Really helpful. everybody should read something like this before starting any coding ! (Now, it;s my turn to review everything that I did)

[shafi rahman]

 

[schmitz koeln]

na ja et jet su

[Izru Garner]

Useful by all people who begin to programming.

[Yun-man Jung]

Thanks a lot. So much useful reference for
novice then.

[I Am a Loser Loser]

Well, the author says: "Common scratch variables for integers are i, j, k, m, n and for doubles x, y and z." However, we should avoid using i and j as variable names because they are by default the unit of imagenary numbers. To be more precise, in Matlab, i^2 == j^2 == -1. Using i and j as varaible names may cause errors hard to detect.

[Mohamed Mostafa]

 

[Jas Ellis]

Very good.

[Krishna Pillai]

Nice doc.

[muhammad islam]

it need more n more improvements for modern age.

[Karthik Raja T]

Good, I will be thankful if u send me any more guidelines materials like complete soft copies..!

[Vishnuvenkatesh Dhage]

Nice and good document

[oliv -]

Several mistakes in that document:
1-The use of underscore is said to be uncommon in other languages, which is a very partial assertion. It is of common use in C, which is quite a common language. This document shows how to write unreadable variable names by not using the underscore.
2- the use of i and j is mentioned for scratch variables. 'i' and 'j' are matlab constants (sqaure root of -1), and redefining 'i' is one of the hardest bug to debug (unless you are well aware of that possibility). The good Matlab programmer should avoid using 'i' (or 'j').
3- Use of uppercase letters in function names is perfectly valid, contrary to what the document suggests. There are cases where X and x have different meanings. Think about colorimetry, where x,y,z are the chromaticity coordinates and X,Y,Z the tristimuli. Matlab offers the freedom of using both uppercase and lowercase, it should be used reasonably (e.g. for an acronym, a name, etc.).

[Asaf Horesh]

I read several gudilines documents, this one was far better than the others.
comment: the use of Capitals in function names is wide spread, and much more clarifying for the meaning.

[Jeff Karas]

Good food for thought. I like the sense of humor, particularly "% 24 November 1971, D.B. Cooper, exit conditions modified."

[Patrick Stallings]

Short, simple, straightforward, and surprisingly helpful.

[Ryan Ollos]

 

[Braden Hancock]

This is great to have! I'm glad I finally have some sort of reference on what are standard accepted practices in more than just my own circle of users.