Darren Duncan

CQL specifies that when we have an operation with both Decimal and Integer inputs, the Integer is promoted to a Decimal and that a Decimal is never changed to an...

While in the general case, the result of a decimal number exponentiated to a decimal exponent might be irrational, it is well known that the result of a decimal exponentiated...

Run the following CQL: ``` define x1: width of Interval[DateTime(2012, 1, 5), DateTime(2012, 1, 25)] define x2: Equivalent(x1, 20 days) define y1: width of Interval[@T05:59:59.999, @T15:59:59.999] define y2: Equivalent(x1, 36000000...

Quantities don't normalize units, giving wrong answers

2

The CQL Engine does not handle unit normalization properly and so comparisons of Quantity of meters and centimeters don't give the right answers. The problem is characterized by that the...

Multiply/Divide with Quantity gives wrong result

4

Per CQL spec 9.6.4 Divide: "For division operations involving quantities, the resulting quantity will have the appropriate unit." Run the following CQL: ``` define x: 1'g/cm3' / 1'g/cm3' ``` Actual...

This is a follow-up to issue #52. The CQL external functions feature deserves a more thorough set of unit tests. An example of such is one that tests a possible...

Display CQL values to the user as valid CQL expression source code

1

This might actually be implemented elsewhere but I consider it a generic issue across multiple components, so am putting it as an Engine issue for now. Currently when evaluating expressions...

Make test suite test uncertainties in some useful way

1

There are currently 6 tests in the CQL portable test suite (XML) that fail specifically because each test question expression results in an uncertainty, and CQL/ELM do not surface uncertainties...

Make Engine validate and correctly handle its own direct inputs

1

The CQL reference implementations are structured of component projects where some of them are kept at arms length intentionally. The CQL Translator and the CQL Engine in particular are kept...

This issue is a followup to issue #52. The CQL Engine needs to validate the outputs of any external functions that it invokes by way of the CQL external function...