On Sat, Nov 19, 2011 at 9:24 AM, Rintze Zelle <[email protected]> wrote: > On Sat, Nov 19, 2011 at 4:53 AM, Sylvester Keil <[email protected]> > wrote: >> >> I think this is altogether too complicated. Either suppression of >> variables should be applied only to printing of variables (not conditions), >> or it should be implemented like Andrea suggests, however, either the >> substitute or the variable that was substituted should be considered to >> exist after the substitution (leading to potentially inconsistent >> conditional results); it just does not make sense to me that suddenly both >> variables should be gone after the substitution. > > My vote is for the former (don't have suppression affect conditionals).
To repeat: I think the language of "suppression" is itself confusing, and that it might need revising. I don't have any particular suggestion ATM though. Bruce ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
