Difference between revisions of "Programming pitfalls"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | [[Category:Pragmatic Programming]] | |
| + | '''Programming Pitfalls: and how to avoid them''' | ||
| − | ==numerics | + | =Introduction= |
| + | |||
| + | =numerics= | ||
examples include odd things with floating point | examples include odd things with floating point | ||
convergence of an algo' | convergence of an algo' | ||
optimisation flags to the compiler can change he results: Lorenz | optimisation flags to the compiler can change he results: Lorenz | ||
| − | + | =save= | |
problems with allocate. Would need to move to a higher level, but more problems if several routines use the same name | problems with allocate. Would need to move to a higher level, but more problems if several routines use the same name | ||
| − | + | =assumed-shape array arguments= | |
useful for information hiding | useful for information hiding | ||
but you need an explicit interface (in the calling code) to make use of them | but you need an explicit interface (in the calling code) to make use of them | ||
Latest revision as of 16:36, 2 September 2008
Programming Pitfalls: and how to avoid them
Introduction
numerics
examples include odd things with floating point convergence of an algo' optimisation flags to the compiler can change he results: Lorenz
save
problems with allocate. Would need to move to a higher level, but more problems if several routines use the same name
assumed-shape array arguments
useful for information hiding but you need an explicit interface (in the calling code) to make use of them