Issue #18942 has been updated by Henrik Lindberg.
Ouch, that was too fast. * This is not !00% backwards compatible (introduces a new keyword). * The precedence is wrong (OR and XOR should not be at the same precedence) * It fails to help with the intended use case (checking mutual exclusivity on a series of parameters; wrongly assumed to produce the correct result when given a xor b xor c, etc. * An xor expression is quite trivial to rewrite using and, or and not. The puppet language does not need this. This addition should be reverted for 3.2. ---------------------------------------- Feature #18942: Puppet should have a xor operator https://projects.puppetlabs.com/issues/18942#change-82169 Author: Erik Dalén Status: Merged - Pending Release Priority: Normal Assignee: Category: parser Target version: 3.2.0 Affected Puppet version: Keywords: xor parser Branch: https://github.com/puppetlabs/puppet/pull/1436 There should be a 'xor' operator in puppet to complement and & or. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
