On 01/08/2014, Michael Anstis <michael.anstis(a)gmail.com> wrote:
I propose the following:
- For a Pattern, with no constraints we exclude the pattern (this is
current XLS behaviour).
e.g. Person( name == $name, age == $age ). If we don't provide values for
$name and $age we don't include the Person pattern. If a user wants to
include the Pattern they'd need to add a constraint "this != null".
If we include the pattern when there are no constraints then it is more
difficult to provide a work-around to exclude the pattern if this is what
some users need (and since it's the existing behaviour; less likely to be
an issue for the majority of XLS users).
- Support escaping String literals with quotes; so a user would enter ""
or " ". This make it obvious that the cell contains a non-null value.
surrounding quotation marks would be stripped before being used in the
If the first character is not the quote character (0x22), assume that
the value in the cell is the actual value of a String. The result to
be used in DRL code will be quoted, and all characters will be escaped
as required according to Java rules.
If the first character is a quote character (0x22), assume that the
value in the cell is a complete String literal, according to Java
rules. It will be used "as is" in DRL code.
WDYT? Should I put this out to the community for opinions too?
With kind regards,