Re: AND/OR expression changes

From: Craig Miskell (cmiskel..lbatross.co.nz)
Date: Sun Jan 19 2003 - 18:31:40 EST

  • Next message: Andrus: "Re: AND/OR expression changes"

    > Application code should work as before, unless somebody was explicitly
    > using ExpressionFactory.binaryExp() for AND/OR (I hope noone did, and used
    > "matchAll", "matchAny", "joinExp" instead). In this case an exception is
    > thrown prompting the user to upgrade to ListExpression.
    >
    > I wonder if instead we should internally create a list expression, and just
    > print a big warning, but do not throw an exception?
    I definitely think it should just be a warning. It's not an exceptional
    condition, just deprecated use of old functionality.

    Craig



    This archive was generated by hypermail 2.0.0 : Sun Jan 19 2003 - 18:32:00 EST