> It's behavior is what it is > because that was necessary to get the job done.
This approach can lead to unexpected side effects. Roman (or was it Nathaniel?) shows how RFNOMNT may be misunderstood to perform two functions when in fact there is only one purpose to it. In addition, only the original requestor and implementor are likely to know of the exceptions whereas anyone who might want to use it may overlook this and find herself on thin ice. With all due respect to those who conceived and coded the function, I think it is unfair to expect no criticism. Without a rationale, one is inevitably tempted to ask whether or not a better solution could be applied. And a rationale is no guarantee against criticism either. ++L
