File Exchange

image thumbnail

MATLAB Style Guidelines 2.0

version 1.0.0.0 (595 KB) by Richard Johnson

Richard Johnson (view profile)
An updated guide to preferred coding style.
4.9
27 Ratings

254 Downloads

Updated 27 Mar 2014

View License

MATLAB has changed just a little in the 12 years since I wrote my previous style guide. This is an updated and revised version.
This document is concerned with 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.
These MATLAB coding recommendations are consistent with best practices in the software development community. The 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.

Cite As

Richard Johnson (2019). MATLAB Style Guidelines 2.0 (https://www.mathworks.com/matlabcentral/fileexchange/46056-matlab-style-guidelines-2-0), MATLAB Central File Exchange. Retrieved .

Comments and Ratings (29)

Ron Fredericks

Ron Fredericks (view profile)

I am still looking for a code style guide that indicates what toolboxes are needed for a given program/script. Currently I run a script then have to wait for error messages to let me know what toolboxes I need to purchase before using a script. It would be nice to quickly understand what toolboxes are needed from within the code base or other mechanism

Hyoki Lee

Hyoki Lee (view profile)

Bassim Younis

Bassim Younis (view profile)

Mark Schreck

Mark Schreck (view profile)

Christos Kaloudas

Christos Kaloudas (view profile)

Edward Bello

Edward Bello (view profile)

Great recommendations, I find myself understanding my own code better!

Weiyang Wang

Weiyang Wang (view profile)

Diego ALMEIDA

Diego ALMEIDA (view profile)

AMAR P

AMAR P (view profile)

Julian Hapke

Julian Hapke (view profile)

I'd be so happy, if everybody who sends me code, would stick to those simple conventions.

Jens Jenewein

Jens Jenewein (view profile)

Jonas Stehli

Jonas Stehli (view profile)

Monika Jaskolka

Monika Jaskolka (view profile)

Tamas Majoros

Tamas Majoros (view profile)

Many thanks

Matthew Kelly

Matthew Kelly (view profile)

Jiang WANG

Jiang WANG (view profile)

Thank you so much for your sharing and efforts since 2003.

David Zhang

David Zhang (view profile)

Valentina Unakafova

Valentina Unakafova (view profile)

Tom Clark

Tom Clark (view profile)

Really good style guide, which is almost identical to the guide we developed internally and independently over many years in-house; we've collapsed onto this guide with minimal effort.

I left off the fifth star for two reasons:

1 - There's no specific naming conventions for classes, as well as class properties and methods. To be fair, TMW's examples of this have varied somewhat in style over the years.

2 - No original text file used to generate the PDF.

@Richard, if you'd like to put this up on GitHub with the base text file, I'd be very happy to collaborate on the class naming?

Jochen Smolka

Jochen Smolka (view profile)

David J. Mack

David J. Mack (view profile)

Very good idea!

Ryan

Ryan (view profile)

Thanks, very useful.

Hilmar Lehnert

Hilmar Lehnert (view profile)

@Richard: This is great stuff. Is it permissable to post this on an internal corporate website for a team to be shared ?

Igor Kuklin

Igor Kuklin (view profile)

No information on proper style of naming of classes (lowercase? camelConvention?) and properties. The .pdf seems to be formatted for very small screens, requires a lot of vertical scrolling vs version 1.5.

Ping Pei

Ping Pei (view profile)

very good

Laurence Montrose

Laurence Montrose (view profile)

best way to prevent mistakes is having a strong style guide - Thanks!

Manuel

Manuel (view profile)

Micah

Micah (view profile)

Excellent style guidelines for MATLAB programming.

Bradley Steel

Bradley Steel (view profile)

MATLAB Release Compatibility
Created with R2013b
Compatible with any release
Platform Compatibility
Windows macOS Linux