<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi!<br>
<br>
On 11/13/2012 05:21 PM, JD Bothma wrote:<br>
</div>
<blockquote
cite="mid:CALeuEBZkGOFjzAfo6F+heYGn18YKGhRJ0ts-cAM-opEwuSgfYg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
The 'ram' option to <a class="moz-txt-link-freetext" href="file:open/2">file:open/2</a> seems to implement some
functionality I want: to treat a file in memory as if it's a file
on disk to let a library support both disk and in-memory data
concisely.
<div><br>
</div>
</blockquote>
Yes, it's ancient functionality that has never been documented. <br>
<blockquote
cite="mid:CALeuEBZkGOFjzAfo6F+heYGn18YKGhRJ0ts-cAM-opEwuSgfYg@mail.gmail.com"
type="cite">
<div>
It doesn't look like this option is documented, but it's
probably useful to many. It looks like it's used by at least
erl_tar.</div>
<div><br>
</div>
<div>Can this become part of the documented API of the file
module?</div>
</blockquote>
Yes, absolutely - we have no intention of removing it. It also has
test suites. Just submit a documentation patch on Erlang-patches and
you have a documented interface!<br>
<blockquote
cite="mid:CALeuEBZkGOFjzAfo6F+heYGn18YKGhRJ0ts-cAM-opEwuSgfYg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>JD</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
Cheers,<br>
Patrik<br>
<blockquote
cite="mid:CALeuEBZkGOFjzAfo6F+heYGn18YKGhRJ0ts-cAM-opEwuSgfYg@mail.gmail.com"
type="cite">
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>