I like the limit of 1024 on simple keys (due to look-ahead concerns).
However, I often use a 'simplified' single-line YAML that uses all
double-quoted strings and in-line forms of mappings and sequences. It's
not easy to read, but it is a cake walk to parse.
On Sat, Jun 26, 2004 at 07:49:18PM +0300, Oren Ben-Kiki wrote:
| On Saturday 26 June 2004 18:58, Jason Diamond wrote:
| > Should there be a line length limit in order to ease the processing of
| > YAML files in typically buffer-challenged environments like C?
| > I would suggest a nice round number like 1024 characters which is so
| > large that humans will never hit it but still allowing for some wiggle
| > room for applications that automatically generate YAML.
| There's a 1024 characters limit for simple keys, to prevent unbound lookahead
| in parsers. We _could_ replace this by having a 1024 characters line length
| limit, I suppose, though that is a much more pervasive restriction.
| > This wouldn't be unheard of: RFC 2822, section 2.1.1 restricts line
| > lengths in email messages::
| > There are two limits that this standard places on the number of
| > characters in a line. Each line of characters MUST be no more than
| > 998 characters, and SHOULD be no more than 78 characters, excluding
| > the CRLF.
| Hmmm. I don't have a strong opinion about this either way - Clark, Brian, what
| do you think?
| > By the way, how's the new draft coming along?
| Slowly ;-)
| Have fun,
| Oren Ben-Kiki
| This SF.Net email sponsored by Black Hat Briefings & Training.
| Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
| digital self defense, top technical experts, no vendor pitches,
| unmatched networking opportunities. Visit http://www.blackhat.com
| Yaml-core mailing list
Clark C. Evans Prometheus Research, LLC
Chief Technology Officer Turning Data Into Knowledge
(main) 203.777.2550 (cell) 203.444.0557