Erlang Central

Hardcoding Expectations

Revision as of 02:55, 11 June 2007 by JeannieLukes998 (Talk | contribs)

cheap diazepam cheap xenical nokia ringtones qwest ringtones zanaflex online diazepam online verizon ringtones free motorola ringtones order lortab prozac online ericsson ringtones but ortho cheap cyclobenzaprine cheap celexa free ringtones phentermine free cool ringtones cheap prozac free qwest ringtones cialis online sprint ringtones nexium online real ringtones sagem ringtones tracfone ringtones free nokia ringtones free punk ringtones mp3 ringtones sony ringtones ativan online but hgh free midi ringtones alltel ringtones cheap flexeril sony ericsson ringtones motorola ringtones vicodin online free tracfone ringtones buy soma levitra online free motorola ringtones cheap didrex cheap sildenafil pharmacy online online zoloft online hydrocodone online free sony ringtones cingular ringtones viagra buy paxil ambien online buy lortab order hydrocodone vigrx online cheap ativan hgh online sildenafil online buy viagra ortho online nextel ringtones lisinopril free funny ringtones free sony ericsson ringtones buy vicodin hydrocodone order ativan mono ringtones clonazepam levitra free sprint ringtones cialis online sony ringtones cheap levitra zanaflex online phentermine celexa online ultracet online wwe ringtones free sharp ringtones buy norco soma online cheap ultracet free cingular ringtones cheap adipex cheap xenical cheap albuterol cheap tenuate cheap ortho free music ringtones sagem ringtones cheap lisinopril meridia online cheap propecia cheap vigrx cheap diethylpropion cheap albuterol mp3 ringtones meridia online free ringtones cheap ultram soma online cheap lortab cheap sildenafil free nextel ringtones cheap lorazepam free funny ringtones diethylpropion online free ringtones funny ringtones cingular ringtones cheap soma nokia ringtones clonazepam online zyban online clomid online buy prozac online valium order lisinopril meridia online buy tramadol sharp ringtones free midi ringtones flexeril online real ringtones celexa online zoloft online free nextel ringtones ericsson ringtones free music ringtones mtv ringtones order ultram buy valium viagra online lorazepam online cheap cialis cheap phentermine buy nexium samsung ringtones cheap norco meridia online sprint ringtones buy rivotril order carisoprodol carisoprodol online cyclobenzaprine online free qwest ringtones free qwest ringtones cheap fioricet verizon ringtones punk ringtones cheap hoodia pharmacy online online tracfone ringtones tramadol cheap rivotril tramadol online didrex online cheap fioricet music ringtones cheap albuterol free nokia ringtones buy viagra buy alprazolam buy xenical pharmacy online online free funny ringtones order zanaflex free ericsson ringtones cyclobenzaprine online adipex online cheap xanax free alltel ringtones free qwest ringtones ultram online sonyericsson ringtones free samsung ringtones cheap lortab free mono ringtones free samsung ringtones zyban online cheap celexa free funny ringtones wwe ringtones cheap rivotril but clomid buy fioricet buy hgh cheap lipitor cheap hoodia clonazepam online cool ringtones tenuate online cheap vicodin real ringtones free sonyericsson ringtones buy hoodia buy tramadol nextel ringtones cheap alprazolam ambien online


Rudolph van Graan


One of the strangest things I had to get used when I started programming in Erlang was to write correct programs (compared to programs that handled all cases). This is one of the fundamental rules in Erlang.

If you look at the code from Nested Cases, you can see through inspection that the function can return one of two possible values: null or {ok,Value}

 1: function(Operation,Values) ->
 2:   case Operation of
 3:     null -> 
 4:       null;
 5:     multiply ->
 6:       do_multiply(Values)
 7:   end.
 9: do_multiply([Value1,Value2]) when integer(Value1),
10:                                   integer(Value2)->
11:   {ok,Value1*Value2}.

The return values for all other input values are not defined. If you write code that uses this function, you might be tempted to write something like this:

 1: main() ->
 2:   Value1 = 10,
 3:   Value2 = 20,
 4:   case function(multiply,[Value1,Value2]) of
 5:     null ->
 6:       {error,unexpected_null};
 7:     {ok,Value} ->
 8:       ... ;Rest of code here
 9:     SomethingElse ->
10:       {error,{unexpected,SomethingElse}}
11:   end.

Note lines 5 and 9. This is in principle very bad code. Keep in mind that you expect the multiply operation to actually return {ok,Value}, the rest doesn't mean anything. In reality you are now forcing the code calling this function to understand details about deeply nested functions. Because you *know* that the multiply funtion will succeed (It is one of your assumptions), it is much better to write:

1: main() ->
2:   Value1 = 10,
3:   Value2 = 20,
4:   {ok,Value} = function(multiply,[Value1,Value2]),
5:   ...

This way, you make it explicitly clear that you expect function(...)to work and to return something like {ok,Value}. If it does not, the function call wil crash and give you a useful diagnostic dump.