RE: [xsl] != vs not(); was Understanding Identity Transformations

Subject: RE: [xsl] != vs not(); was Understanding Identity Transformations
From: "Pawson, David" <David.Pawson@xxxxxxxxxxx>
Date: Mon, 14 Feb 2005 10:53:47 -0000
    -----Original Message-----
    From: David Carlisle
    >So which would you advise to solve the question?
    > "@cat and not(@cat='BLUE')"
    > or
    > "@cat!='BLUE'"

    (Almost) Never used != if one or both arguments is a node
    set. Even in those cases where it does do what you want,
    you have to think so hard each time to convince yourself
    that's what you mean, that it always ends uo makin the
    stylesheet harder to debug later.

    If A is a node set with two or more nodes that are not
    string-equal then A != x is always true for any value of x.
    This is an entirely logical result of the fact that infix
    operators so an "if exists" over the whole node set, but
    it's so rarely what you want that I try to avoid != as much
    as possible.

Is this any more clear in XSLT 2.0?
I'm thinking of the changes relating to taking the first-node of a node-set
as the string value?

regards DaveP

** snip here **


NOTICE: The information contained in this email and any attachments is
confidential and may be privileged.  If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227


Current Thread