My preference, although Igor is case insensitive, is to start global objects with uppercase and local objects with lowercase. Global variables, however, start with lowercase g followed by an uppercase letter starting the meaningful part of the name.
We here at WaveMetrics often start non-static functions with WM to minimize conflict with user code. You might consider something similar if you are writing a package to be used by others.
I've created a new project here.
It holds coding conventions and best practices I've come up with for Igor Pro. They try to be exhaustive, and therefore also hold special things like doxygen formatting and whitespace rules.
I'm actively using these conventions on large projects.
My preference, although Igor is case insensitive, is to start global objects with uppercase and local objects with lowercase. Global variables, however, start with lowercase g followed by an uppercase letter starting the meaningful part of the name.
We here at WaveMetrics often start non-static functions with WM to minimize conflict with user code. You might consider something similar if you are writing a package to be used by others.
Larry Hutchinson
WaveMetrics
support@WaveMetrics.com
March 6, 2016 at 09:50 am - Permalink
It holds coding conventions and best practices I've come up with for Igor Pro. They try to be exhaustive, and therefore also hold special things like doxygen formatting and whitespace rules.
I'm actively using these conventions on large projects.
March 12, 2016 at 08:47 am - Permalink