Re: [Yaml-core] meeting minutes 20 jun 2002

[Clark C . E. <cc...@cl...>]

On Sat, Jun 22, 2002 at 03:31:40AM -0400, Oren Ben-Kiki wrote:
| If we agree that comments interleaved within an unquoted scalar are not
| allowed, we remove this special case and return to the rule that "comments
| can't appear inside any scalar". That's better.

Ok.

| To keep things clear this means that inside an in-line collection, comments
| can only appear after a ',' ':' ']' '}', like this:
| 
| in-line: { key: # comment
|            value, # comment
|            and: so on } # comment 
| 
| In top-level it would be OK to write:
| 
| this: text # comment
| 
| But not:
| 
| error: text # comment
|        next

Sounds good.  I think Brian was wanting to allow comments
to appear after a quoted value but before the comma, as in;

  this: [ "Is what Brian "  # comment
        , "would like to see" ]

If this is too much of a special case in the productions
we can leave it out for now (erring on the restrictive side).
Later on if we can add it if it turns out not to be hard.

| This means thete's no reason not to allow multi-line unquoted values in
| in-lines (we allow multi-line quoted and Clark's reason about comments no
| longer holds). For example:

Yes, this works then; it handles my problem.   We are still NOT
allowing multi-line unquoted for keys, right?  This is just
butt ugly and it is what the ? construct is for...

| Another unrelated relaxation I want to work into the productions: I think
| that #+ should only start a comment if it is _surrounded_ by spaces.
|
| Example:
| 
| - text ######
| - text # comment
| - text ######
| - text with #17 or 17# etc. # Comment

Ok.

Clark

P.S.  I'm going to bounce a private thread regarding
vim syntax highlighting to the list.