HELP nits

[Steve Fabian]

Topics f_attrib.htm and f_wattrib.htm both refer to optional file selection by attribute. This is not applicable to these functions.

It is unclear that when only one parameter (a filename) is used, both functions display all attributes.

It is not reported that if you specify an extended, NTFS-only attribute in @ATTRIB that attribute is considered to be OFF regardless of its actual state, and in the absence of the optional third, P, parameter will result in the function returning 0 regardless of the state of any other selected attribute.

It is very difficult to locate the interpretation of the optional third, P, parameter of @ATTRIB.
--
Steve

 

[rconn]

Topics f_attrib.htm and f_wattrib.htm both refer to optional file selection by attribute. This is not applicable to these functions.

That's deliberate, as the "Attribute Switches" topic has additional information on attributes.

It is unclear that when only one parameter (a filename) is used, both functions display all attributes.

@ATTRIB states this explicitly. @WATTRIB says it is similar to @ATTRIB, but admittedly doesn't repeat the contents of @ATTRIB.

It is not reported that if you specify an extended, NTFS-only attribute in @ATTRIB that attribute is considered to be OFF regardless of its actual state, and in the absence of the optional third, P, parameter will result in the function returning 0 regardless of the state of any other selected attribute.

The help says you should use @WATTRIB to query the extended attributes. The two functions are very different (for historical and compatibility reasons), and you cannot treat them as identical.

@ATTRIB (as documented) queries Windows for the attributes and then strips off all the extended attributes before comparing with your argument. This definitely will *not* change, as it would break backwards compatibility.