From: Oren Ben-K. <or...@ri...> - 2002-05-20 13:47:04
|
Clark C . Evans [mailto:cc...@cl...] wrote: > So. I think the proposal is to use | to signify "scalar", > and still adorn it with \ escape and - chomp. Then, > we add a "fold" format for strings. > > --- > this: | !str|fold > is a folded > scalar value > > Anyway, the big concern I have is that formats are currently > specific to a given type family. Thus, if we followed the current > pattern, the "fold" format would be specific to the !str type. I think that's a show-stopper. > Hmmm. Perhaps folding could just be yet-another-indicator > attached to the pipe so that | means scalar (by default block) > and |^ could mean folded. In this way, |^\- would mean a folded, > escaped, chomped scalar. I think this may be a better solution > as I do agree that ] vs | is not-so-intuitive. That's merely an alternate notation for the exact same concept. Easy enough to do. While ] isn't exactly the most... graceful... indicator for folded, I'm not certain |^ is much of an improvement. Hmmm... How about '>'? This works well either as standalone: | |\ |- |\- > >\ >- >\- Or as a modifier for |: | |\ |- |\- |> |\> |>- |\>- I could live with that... Thoughts? Have fun, Oren Ben-Kiki |
From: Brian I. <in...@tt...> - 2002-05-20 18:43:30
|
On 20/05/02 09:48 -0400, Oren Ben-Kiki wrote: > Clark C . Evans [mailto:cc...@cl...] wrote: > | |\ |- |\- > > > >\ >- >\- > > Or as a modifier for |: > > | |\ |- |\- > > |> |\> |>- |\>- > > I could live with that... Thoughts? I seem to remember a certain someone thinking of this a few months ago: On 15/01/02 07:34 -0000, Oren Ben-Kiki wrote: > Brian Ingerson [mailto:in...@tt...] wrote: > > 3) '^' as an indicator kinda blows. It seems a little confusing. I'd > > like to YAC about switching it to '>'. This still has the 'folded' > > connotations of '^' but it points forward instead of up. > > I dislike it because it would make '>' be an indicator. Besides, a > standalone '>' shouts "greater than" to everyone, while '^' says "magic" - > in different contexts it stands for "power", "control", "start of line"... > Giving it a specific magical meaning in YAML is better than subverting '>'. Cheers, Brian |
From: Clark C . E. <cc...@cl...> - 2002-05-20 19:02:35
|
On Mon, May 20, 2002 at 11:43:25AM -0700, Brian Ingerson wrote: | I seem to remember a certain someone thinking of this a few months ago: *grins* Seriously, how about the semi-colon? It will let us do all kinds of cutsy things with multi-line scalars! Then we can even call it the "personality" of the scalar. personality: boring: | plain scalar straight: |-; chomped, folded happy: |; \ folded, escaped weirdo: |;-\ folded, chomped, escaped blind: |-\ chomped, escaped |;-\ Clark |
From: Clark C . E. <cc...@cl...> - 2002-05-20 18:44:58
|
| > Anyway, the big concern I have is that formats are currently | > specific to a given type family. Thus, if we followed the current | > pattern, the "fold" format would be specific to the !str type. | | I think that's a show-stopper. Agreed, cuz I like Brian's suggestion. That said, I think having another modifier character may be a better approach. | | | |\ |- |\- | | |> |\> |>- |\>- | | I could live with that... Thoughts? I don't like it... too much like robo-cop. Hmm. Either Ryan or Steve suggested that we use letters or even alpha strings, like... |fold,escape,chomp -- with possible abbreviation like |f,e,c Given that the case of a multi-line scalar, there is often a good amount of space, perhaps the non-abbrev version would look good. However, I tend to lock onto words as content, and thus I feel that although fold, escape, chomp spelled out may be intuitive it will also make the file hard to read as your eye locks in on them rather than the content. How 'bout the semi-colon? sig: |;-\ Clark |
From: Brian I. <in...@tt...> - 2002-05-21 13:25:00
|
I think we're missing the whole point of what I really want here. Clark alluded to it but, what I really want is the ability to extend the multiline leaf formats that we support. One very useful format would be a mix of block and folded. Lines beginning with whitespace (as content) would be block. Lines beginning with non-whitespace would be folded. I see this pattern in textual data all the time. (If you know Perl, think POD) Anyway, we'll probably want to extend our multiline styles. I proposed to Clark that 'folded' was merely another string format like 'mixed'. Everything could be specified using our current block format with some kind of format or style modifier. And the reformatting would be done at the Loader level, not by the Parser. How about: --- <multi style="mixed" chomp="no"> To encode data type and other application semantics in a YAML serialization, every node has a type family and leaf nodes have a syntax format. invoice: 34843 date : 2001-01-23 buyer: given : Chris family : Dumars product: - Basketball: 4 - Superhoop: 1 D1 Implicit family and format ... Cheers, Brian |