rename MT_VOID to MT_EMPTY

This commit is contained in:
John Kerl 2016-04-13 09:13:02 -04:00
parent ca981e028f
commit ed3eca2476
2 changed files with 8 additions and 8 deletions

View file

@ -1279,7 +1279,7 @@ Rather, records lacking one or more sort keys are simply output contiguously by
<ul>
<li/> <b>Void</b>: a field name is present in a record (or in an out-of-stream
<li/> <b>Empty</b>: a field name is present in a record (or in an out-of-stream
variable) with empty value: e.g. <tt>x=,y=2</tt> in the data input stream, or
assignment <tt>$x=""</tt> or <tt>@x=""</tt> in <tt>mlr put</tt>.
@ -1297,13 +1297,13 @@ Rules for null-handling:
<ul>
<li> Records with one or more null (void or absent) sort-field values sort
<li> Records with one or more null (empty or absent) sort-field values sort
after records with all sort-field values present:
POKI_RUN_COMMAND{{mlr cat data/sort-null.dat}}HERE
POKI_RUN_COMMAND{{mlr sort -n a data/sort-null.dat}}HERE
POKI_RUN_COMMAND{{mlr sort -nr a data/sort-null.dat}}HERE
<li> Functions/operators which have one or more <i>void</i> arguments produce void output: e.g.
<li> Functions/operators which have one or more <i>empty</i> arguments produce empty output: e.g.
POKI_RUN_COMMAND{{echo 'x=2,y=3' | mlr put '$a=$x+$y'}}HERE
POKI_RUN_COMMAND{{echo 'x=,y=3' | mlr put '$a=$x+$y'}}HERE
POKI_RUN_COMMAND{{echo 'x=,y=3' | mlr put '$a=log($x);$b=log($y)'}}HERE
@ -1324,7 +1324,7 @@ The reasoning is as follows:
<ul>
<li/> Void values are explicit in the data so they should explicitly affect accumulations:
<li/> Empty values are explicit in the data so they should explicitly affect accumulations:
<tt>mlr put '@sum += $x'</tt>
should accumulate numeric <tt>x</tt> values into the sum but an empty
<tt>x</tt>, when encountered in the input data stream, should make the sum

View file

@ -4769,7 +4769,7 @@ Rather, records lacking one or more sort keys are simply output contiguously by
<ul>
<li/> <b>Void</b>: a field name is present in a record (or in an out-of-stream
<li/> <b>Empty</b>: a field name is present in a record (or in an out-of-stream
variable) with empty value: e.g. <tt>x=,y=2</tt> in the data input stream, or
assignment <tt>$x=""</tt> or <tt>@x=""</tt> in <tt>mlr put</tt>.
@ -4787,7 +4787,7 @@ Rules for null-handling:
<ul>
<li> Records with one or more null (void or absent) sort-field values sort
<li> Records with one or more null (empty or absent) sort-field values sort
after records with all sort-field values present:
<p/>
<div class="pokipanel">
@ -4826,7 +4826,7 @@ x=9,b=10
</div>
<p/>
<li> Functions/operators which have one or more <i>void</i> arguments produce void output: e.g.
<li> Functions/operators which have one or more <i>empty</i> arguments produce empty output: e.g.
<p/>
<div class="pokipanel">
<pre>
@ -4896,7 +4896,7 @@ The reasoning is as follows:
<ul>
<li/> Void values are explicit in the data so they should explicitly affect accumulations:
<li/> Empty values are explicit in the data so they should explicitly affect accumulations:
<tt>mlr put '@sum += $x'</tt>
should accumulate numeric <tt>x</tt> values into the sum but an empty
<tt>x</tt>, when encountered in the input data stream, should make the sum