Defect in XSH unlink

[yyyyyy@xxxxxxxxxxxxx]

        Defect report from : Andrew Josey , The Open Group

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 1555 line 47966 section unlink comment {unlink-eisdir}

Problem:

Defect code :  3. Clarification required

The unlink() function defines the following error condition

[EPERM] The file named by path is a directory, and either the calling process 
does not
 have appropriate privileges, or the implementation prohibits using unlink()
 on directories.


The EISDIR error condition would also seem an appropriate error
to return in the case when unlink() is attempted on a directory.

Is an implementation conforming that returns EISDIR rather
than EPERM ?

A certain body of implementors believe that this is the more
natural error code to expect in this case.

Action:

Proposed interpretation:

The standard is clear on the requirements, however concerns should
be forwarded to the sponsor to consider allowing the EISDIR
error.


Proposed rationale:

Applications receiving an error should be able to cope with
any unexpected error code. The EISDIR code would seem a logical
return.