Databases
StackOverflow2013
Postsdbo
POerlang phylosophy: Should I let users deal with wrong input or not?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POerlang phylosophy: Should I let users deal with wrong input or not?
    primarykey
    data
    text
    <p>This is the case:</p> <pre><code>% print/1: Prints out the integers between 1 and N print(0) -&gt; io:format("~w~n", [0]); print(N) when is_integer(N) -&gt; io:format("~w~n", [N]), print(N - 1). </code></pre> <p>If the user inputs a non-integer, this happens:</p> <pre><code>11&gt; effects:print('alfalfa'). ** exception error: no function clause matching effects:print(alfalfa) </code></pre> <p>Is about phylosophy: Should I correct my program this way, in order to 'catch all' kinds of input?</p> <pre><code>% print/1: Prints out the integers between 1 and N print(0) -&gt; io:format("~w~n", [0]); print(N) when is_integer(N) -&gt; io:format("~w~n", [N]), print(N - 1). % Last Line added: print(_Other) -&gt; false. </code></pre> <p>I'm new in erlang. Is there some convention for dealing with this?</p> <p>Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USalain.janinm
    1. USHerman Junge
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POerlang phylosophy: Should I let users deal with wrong input or not?
      1. USMuzaaya Joshua
      1. VTFavorite
    2. VO
      singulars
      1. POerlang phylosophy: Should I let users deal with wrong input or not?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POerlang phylosophy: Should I let users deal with wrong input or not?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload