<div dir="ltr">You also have file:eval/1 and file:script/1. (And "path_..." versions of the same.)</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><br> /Richard</div></div>
<br><div class="gmail_quote">2017-12-05 4:51 GMT+01:00 Richard A. O'Keefe <span dir="ltr"><<a href="mailto:ok@cs.otago.ac.nz" target="_blank">ok@cs.otago.ac.nz</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
On 4/12/17 8:21 PM, bengt e wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Greetings,<br>
<br>
Is 2) similar enough to file:consult/1, to maybe warrant it to be called<br>
'consult' instead?<br>
</blockquote>
<br></span>
file:consult/1 reads a file and (all going well) *returns a list of the<br>
terms* but does not process them. This isn't all _that_ much like what<br>
(shell):include/1 is supposed to do. import(...) was designed to mimic<br>
the -import directive and include(...) was designed to mimic the<br>
-include directive.<br>
<br>
I was actually thinking of it as analogous to the<br>
'source <filename>' command in dbx, but using a name<br>
already familiar to Erlang programmers.<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<wbr>_________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org" target="_blank">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" rel="noreferrer" target="_blank">http://erlang.org/mailman/list<wbr>info/erlang-questions</a><br>
</div></div></blockquote></div><br></div>