From: Brian I. <in...@tt...> - 2001-12-04 05:27:39
|
Oren, It turns out to be a good thing that we switched from '=' to ':' in inline maps. Now we can write: - !ref =: foo as: - !ref {=: foo} instead of: - !ref {'='= foo} Kinda nice :) Cheers, Brian |
From: Clark C . E. <cc...@cl...> - 2001-12-04 05:51:31
|
| - !ref {=: foo} Hmm. So the preview examples I have are an error beacuse the space is missing? - !point {x:73,y:129} So this would have to be re-written as... - !point {x: 73,y: 129} Hmm. I guess this is necessary to enable the use of dates: {when: 20:20 PM } Fiddlesticks... that's ugly. Let's force dates to be quoted in this case... no? So, it becomes {when:'20:20 PM'} I guess this is an "exception" in the rule, but allowing the "packing" for data points is probably more important for useability. If we go this way, brian can write... - !ref {=:foo} Clark |
From: Brian I. <in...@tt...> - 2001-12-04 06:04:30
|
On 04/12/01 01:03 -0500, Clark C . Evans wrote: > | - !ref {=: foo} > > Hmm. So the preview examples I have are an error > beacuse the space is missing? > > - !point {x:73,y:129} > > So this would have to be re-written as... > > - !point {x: 73,y: 129} > > Hmm. I guess this is necessary to > enable the use of dates: {when: 20:20 PM } > Fiddlesticks... that's ugly. Let's force > dates to be quoted in this case... no? > So, it becomes {when:'20:20 PM'} Nope. Then Oren can't have time data implicitly transfer. I thought we went over this yesterday. The current rule is that '- ' is the sequence bullet and ': ' is the key/value separator. Always. I'm comfortable with it. And Oren's limitations on implicit scalars made recursive/implicit parsing of inline collections, not be a total nightmare. Packing would be nice, but thems the breaks. > I guess this is an "exception" in the rule, > but allowing the "packing" for data points > is probably more important for useability. > If we go this way, brian can write... > > - !ref {=:foo} I'd rather support Oren's time data. Cheers, Brian |