[m-rev.] splitting io.m

Julien Fischer jfischer at opturion.com
Tue Aug 18 11:28:19 AEST 2015


Hi,

On Tue, 18 Aug 2015, Peter Wang wrote:

> On Mon, 17 Aug 2015 17:48:39 +1000 (AEST), "Zoltan Somogyi" <zoltan.somogyi at runbox.com> wrote:

...

> I'm not interested a wide-ranging break of the io.m interface (even with
> a transition period), if that is what is proposed.  It would annoy me
> greatly as a user as it does not seem justified.  I don't think after
> the whole exercise our programs would be particularly improved.
>
> Aside from the main functionality of reading/writing/opening/closing
> files, there are also:
>
> - prolog-style see/seen/tell/told [1]
> - progname
> - command_line_arguments
> - exit_status
> - globals [1]
> - environment variables
> - make_temp
> - remove file, rename file, symlinks, file access, file type, file modtime
> - report_stats [2]
> - call_system
>
> I would have no qualms about deprecating [1]

Ditto for prolog style see/seen/tell/told.   I'd suggest eventually
moving them into the prolog module since that is the designated prolog
compatibility layer.

The I/O globals currently support a thread safe update operation that
mutables don't have, so the two aren't quite equivalent.

> and moving [2].

Into benchmarking presuambly?

Cheers,
Julien.



More information about the reviews mailing list