From: Clark C . E. <cc...@cl...> - 2002-06-18 00:53:30
|
| I don't see much of a problem Clark. Remember the simple principle that when | dealing with inlines, you first simply (conceptually) join all of the lines | within the current indentation level. After that you simply parse as if it | were all one big line. I'm more taken back by the added complexity. It just allows for just a few too many ways to do it... if you have a multi-line string, just use folded or block, no? I also remember that we had some issues, especially using keys, but I can't recall specifics at the moment. Overall, are you sure the added complexity is worth it? --- Hi Ho, Kermit The Frog here with yet another Muppet News Flash: Today in the news the Cookie Monster has given up cookies! Let's go right to the source and ask the monster himself: Cookie Monster, how is life without Cookies? "Ohh! Cookies! Yum Yum : What would I do without Cookies!" | The inline spanning multiple lines is little more than a line continuation | feature. Please show me some examples where this breaks down. I'm less concerned with it breaking down than with it adding a bunch of unneeded complexity. | Also remember that you can't use nesting indicators (? | >) within inlines. | So I think that you really do want to support scalars spanning lines. Why? If your in-lines are that big, you shoudn't be using inlines. It's pretty simple. By not allowing for multi-line scalars we enforce good practice; making YAML easy to read. Otherwise we just make 1000's of ways people can do it. I was initially proposing allowing in-line collections to span multiple lines to _enhance_ readability; allowing for quoted or simple scalars to span multiple lines _reduces_ readability. Clark |