Lindsay:
>>>2) The brackets don't appear to nest.
>>
>>Oddly enough, I believe they do, but they've chosen syntax (as I
>>understand it) that doesn't make it obvious, at least to my eye.
>>Paraphrasing their examples a bit, the basic tagging seems to
>>go like this:
>
> Well I disagree. (Who would have thought it!) I think nesting requires
> you to obey the conventional usage of brackets - opening and closing -
> and these examples surely don't do that for } and { (Sure they nesy
> in some way, but [not] in the way that people would expect them to)
I agree it's odd, but they aren't using '}' and '{' as matching brackets per
se, but rather as 'end-of-opening-element' and 'beginning-of-closing-element'
markers, complementing the use of '[' and ']' as 'beginning-of-opening-element'
and 'end-of-closing-element' markers.
That they're widely used in many contexts as simple matching brackets, and
that XML's syntax for '<' and '>' leads one to expect them to match up,
are just further arguments against using them like this in a related context.
I actually can't think of any other context where you'd expect '[' and '}' to
delineate some token or expression, with '{' and ']' delineating some complementary
token or expression. The closest I can think of is the mathematical range delimiters,
where things like [0,10), [-1,1], (x,y] and (-50,50) all make sense, but even then,
there's no requirement for them to come in pairs of the form [..) ... (..] .
--
Frank Wales [[EMAIL PROTECTED]]
- Automatic footer for [EMAIL PROTECTED] ----------------------------------
To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss
To join the announcements list, mail [EMAIL PROTECTED] subscribe announce
To receive a help file, mail [EMAIL PROTECTED] help
This list is archived at http://www.mail-archive.com/discuss%40ppig.org/
If you have any problems or questions, please mail [EMAIL PROTECTED]
