> On Sun, 9 Nov 2003, Courier User wrote: > >> In trying to debug some problems in a program that I'm invoking via >> xfilter in maildrop, I have realized that the following construct in >> a maildrop recipe file doesn't do exactly what I expected: >> >> VARIABLE="" >> >> In this case, maildrop completely removes the environment variable >> called "VARIABLE". I was expecting that it would cause that >> variable to exist and to be bound to an empty string. >> >> A new function called unset() or something similar would be used to >> completely remove a variable from the environment; i.e., >> >> unset(VARIABLE) > > I guess I'd prefer "unset VARIABLE" to "unset(VARIABLE)" to have > a closer analogue to "VARIABLE=foo" rather than "set(VARIABLE,foo)" > and so on.
The maildrop software already has an infrastructure for implementing functions of the form function([arg,...]) The "unset" capability could be easily implemented using this infrastructure. To do it without parentheses seems to be a more complicated task, as it probably would involve a major overhaul of this infrastructure. -- Courier User [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
