> Seems like the xml parser has it's own logic when dealing with lists - are
> there reserved props like !CHARDATA that don't throw errors if there's no
> value? Dig this:
>
> put blist[1].audioresponse.directive
> -- ["!ATTRIBUTES": [:]]
>
> --- notice there's no "!CHARDATA"; now:
>
>
> put blist[1].audioresponse.directive["!CHARDATA"]
> -- <Void>
>
> I get a void. But if I do something like 'put blist.bob' where there's no
> 'bob' prop, of course I get an alert.
That's not unique to the xml parser; it's related to how you're accessing
your properties.
aList = [#you: "grimm", #me: "not"]
put aList.you
-- "grimm"
put aList.him <<-- script error: property not found
put aList[#him]
-- <Void>
Moral: bracket access = no error, dot syntax = error (when accessing
non-existent properties)
HTH,
-Sean.
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
