Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Courier User writes:
>
>
>> Could someone (Sam?) explain why that 'delete' statement exists? Is
>> there part of maildrop or courier that depends on this odd behavior?
>
> Because if variable FOO is not defined, $FOO defaults to an empty string.
>
> Logically, the converse should also be true.
But the converse varies greatly from the way that most software that I
know of functions. It seems contrary to "the principle of least
surprise" ("PoLS") to have A be equivalent to B, instead of C:
A: (in maildrop)
SENDER=""
B: (in an xfilter program)
getenv("SENDER") == NULL /* contrary to PoLS */
C: (in an xfilter program)
getenv("SENDER") != NULL /* adheres to PoLS */
In other words, in most software I know of, A => C. But in maildrop,
A => B.
--
Courier User
[EMAIL PROTECTED]
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
