On adding `/`, my projected usage of yaml is limited to s11n and c11n, and I
have looked at every instance where a path is mentioned. This amounted to
168 paths. In every case bar 3 adding adding `/` as a legal initial
character would allow the path to be unquoted. The 3 odd cases were regular
expression / glob patterns that no sane person would not quote. if `\` was
not allowed, then I would simply replace it with `/`
On comments: as long as I can unambiguously comment out lines I don't care
what is used, its unlikely to be as painful as XML.
On spec creep, I mentioned Yaml to a collegue, he spent 10 minutes doing
research, I suspect readign the list archives as he commented "It's been
going a while and it's still not stable". He seemed to think that it was a
bad indication that there were 3 different parsers and no C parser. I
respect this guys opinion, he has been a bit of a mentor to me, and has
always picked up on new tech early.
If a sufficient condition for a rock solid C parser is a frozen spec, then
do it. Then I can start using Yaml in our core products.
Tom Harris, Software Engineer
Optiscan Imaging, 15-17 Normanby Rd, Notting Hill, Melbourne, Vic 3168,
email tomh@... ph +61 3 9538 3333 fax +61 3 9562 7742
This email may contain confidential information. If you have received this
email in error, please delete it immediately,and inform us of the mistake by
return email. Any form of reproduction, or further dissemination of this
email is strictly prohibited. Also, please note that opinions expressed in
this email are those of the author, and are not necessarily those of
Optiscan Pty Ltd.