[MLton-devel] Posix.FileSys.pathconf

[Stephen Weeks]

> Am I totally wrong when I think the original intention was to have a map
> between:
> 
> true 	=== 	SOME 1
> false	===	SOME 0
> __!__	===	NONE
> 
> where __!__ is the domain-theoretic bottom. It will have the advantage
> that it enables the ML-part of the interface to cope with undefined
> behaviour in the Posix semantics.

I don't thing the intention of the Basis Library spec was to leave
NONE for undefined Posix behavior.  It says that NONE should be
returned for unbounded integer values and does not allow NONE to be
returned for boolean values (like _PC_SYNC_IO).

> As I read the NetBSD documentation they specifically say that upon
> returning -1, there will be situations in which the errno is not set[1]

Right.  The Linux and SunOS man pages along with the NetBSD say that
those situations are the ones when the integer value is unbounded,
hence are precisely the ones where the SML pathconf should return
NONE.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel