Erlang (programming language)/Tutorials/Advanced syntax: Difference between revisions
Jump to navigation
Jump to search
imported>Eric Evers (New page: There are some strang elemente of erlang syntax, some of which are caused by the need of parallel programming and functional programming. Each if structure must have a true conditional ...) |
imported>Eric Evers No edit summary |
||
| Line 1: | Line 1: | ||
There are some strang elemente of erlang syntax, some of which are caused by the | There are some strang elemente of erlang syntax, some of which are caused by the | ||
need of parallel programming and functional programming. | need of parallel programming and functional programming. | ||
Each if structure must have a true conditional branch. | Each 'if' structure must have a true conditional branch. | ||
If a variable is assigned(matched) in one branch of an if or case sturcture and used | If a variable is assigned(matched) in one branch of an 'if' or 'case' sturcture and used | ||
after that structure then the variable must be assigned(matched) | after that structure then the variable must be assigned(matched) | ||
in all the branches. | in all the branches. | ||
Revision as of 18:41, 1 September 2008
There are some strang elemente of erlang syntax, some of which are caused by the need of parallel programming and functional programming.
Each 'if' structure must have a true conditional branch. If a variable is assigned(matched) in one branch of an 'if' or 'case' sturcture and used after that structure then the variable must be assigned(matched) in all the branches.
Guard expressions are restricted to only builtin functions. This is generally not a problem becuase on can precalculate values from non-builtin functions before the guard and then use the value in the guard expression. Restricting functions in guards protects from side effects and may increase speed.