Re: Literal for plain style string

"Clark C. Evans" <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <[email protected]>
On Sun, Aug 12, 2007 at 05:19:26PM -0700, TRANS wrote:
| >     ---
| >     - This is a paragraph
| >       that continues on the
| >       third line.
| >     - this is a # comment
| >     -
| >       # this is also a comment
| >       but this isn't
| >
| > This is currently equivalent to:
| >
| >     ['This is a paragraph that continues on the third line.',
| >      'this is a', "but this isn't"]
| >
| > I'm not exactly clear what the proposed rewrite would be.
| 
| I think this is how it would be, which I think are the simplest interpretations:
| The first would come out as if we currently did:
| 
|     - |
|       This is a paragraph
|       that continues on the
|       third line.
| 
| For the second case, I think it is reasonable to specially handle
| comments. So it would come out the same as it does now. To keep "#
| comment" in the string, start the text on a new line.
| 
| In the third case, yes, it wouldn't be a comment any more. Though we
| could make this a minor distinction between plain and "hard" literal
| if we really wanted, but I doubt that's necessary, but maybe the
| comment could start on the line with the '-' indicator and be okay?

The point of the examples was to demonstrate that this isn't a simple
change -- I'm sure there are other cases that are just as problematic.
I'll consider the proposal a bit more formal if you review the entire
specification and correct it to handle the particular changes you
have in mind, as well as updating the regression tests in Kirill's
implementation -- in a branch, of course.  *grins*

The fact is, even if we could agree that this is a good idea, which
I'm not convinced of, the amount of implementation effort exceeds my
bandwith.  We've not been able to even keep up with minor fixes let
alone a massive change like this.

Cheers,

Clark

-------------------------------------------------------------------------
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/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.