If: Difference between revisions

1 byte added ,  27 October 2016
no edit summary
(Created page with "This, adapted from Wikipedia’s article on “Conditional (computer programming)” works equally well for the legal if: {{box| == If–then(–else) == The <code>if–...")
 
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
This, adapted from Wikipedia’s article on “Conditional (computer programming)” works equally well for the legal [[if]]:
This, adapted from Wikipedia’s article on “Conditional (computer programming)” works equally well for the legal [[if]]:


{{box|
===The computer-code if===
== If–then(–else) ==


The <code>if–then</code> construct (sometimes called <code>if–then–else</code>) is common across many programming languages. Although the syntax varies quite a bit from language to language, the basic structure looks like this:
The <code>if–then</code> construct (sometimes called <code>if–then–else</code>) is common across many programming languages. Although the syntax varies quite a bit from language to language, the basic structure looks like this:


<syntaxhighlight lang="qbasic">
  If (boolean condition) Then
  If (boolean condition) Then
     (consequent)
     (consequent)
Line 12: Line 10:
     (alternative)
     (alternative)
  End If  
  End If  
</syntaxhighlight>


When a [[mediocre lawyer|lawyer]] finds an <code>If</code>, {{sex|he}} expects a boolean condition – for example, <code>x > 0</code>, which means “the variable x contains a number that is greater than zero” – and evaluates that condition. If the condition is <code>true</code>, the statements following the <code>then</code> are executed. If not, the execution continues in the following branch – either in the <code>else</code> block (which is usually optional), or if there is no <code>else</code> branch, then after the <code>end If</code>.
When the machine finds an <code>If</code>, it expects a boolean condition – for example, <code>x > 0</code>, which means “the variable x contains a number that is greater than zero” – and it evaluates that condition. If the condition is <code>true</code>, the statements following the <code>then</code> are executed. If not, the execution continues in the following branch – either in the <code>else</code> block (which is usually optional), or if there is no <code>else</code> branch, then after the <code>end If</code>.


After either branch has been executed, control returns to the point after the <code>end If</code>.
After either branch has been executed, control returns to the point after the <code>end If</code>.
}}


It is to just this kind of simplicity and functional clarity that a legal contract ought to aspire. But heres the difference: A computer coder depends on a dumb client to faithfully interpret and flawlessly implement his code. If it doesn’t, his programme won’t work.  A lawyer relies on his dumb client to come back to him and ask him what it all means.
===The legal if===
It is to just this kind of simplicity and functional clarity that a legal contract ought to aspire. But here’s the difference: Computer code depends on a dumb client to faithfully interpret and flawlessly implement the code. If it doesn’t, his programme won’t work.  A [[Mediocre lawyer|lawyer]], by contrast, depends on his dumb client getting confused and coming back to ask what it all means.


So the diligent lawyer writes not with clarity and simplicity, but densely and with {{tag|flannel}}. The most basic of operators - [[if]] - he renders as “[[in the event that]]. A single conjunction replaced by a [[preposition]], a [[definite article]], a [[noun]] and a different [[conjunction]].
So the diligent lawyer writes not with a coder’s clarity and simplicity, but densely and with {{tag|flannel}}. The most basic of operators - [[if]] - he renders as “[[in the event that]]. A single [[conjunction]] replaced by a [[preposition]], a [[definite article]], a [[noun]] and a different [[conjunction]].




{{plainenglish}}
{{plainenglish}}