Re: Literal for plain style string

On 8/16/07, Ingy dot Net <[email protected]> wrote:
> Hi Trans,
>
> We've been discussing this a bit and it seems to have come to an abrupt halt.
>
> Clark and Oren and I were considering the change that we:
>
>   1) Outlaw a plain scalar starting on a new line
>   2) Make the '|' be optional
>
> This is way less onerous than simply changing the folding property of all
> plain scalars.
>
> Then you could do:
>
>     ---
>     paths1: |
>       some/file/path1
>       some/file/path2
>       some/file/path3
>     paths2:
>       some/file/path1
>       some/file/path2
>       some/file/path3
>
> where both mapping values are equivalent.
>
> But Kirill pointed out that this would be ambiguous:
>
>     ---
>     foo:
>       bar: baz
>
> and that pretty much kills the idea.

I thought of that too, but then I realized, it really already is
ambiguous. What keeps that example from being a string but the fact
that the first line has the colon in it (essentially)? To prevent that
one would still need the |. Or possibly the first line would have to
be indented.

That seems to make sense to me at least. Or is their something I'm
misunderstanding?

Thanks,
T.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/