Skip to content

Instantly share code, notes, and snippets.

@ingydotnet
Last active December 6, 2017 18:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ingydotnet/6ff14305d5815cafb920111c051cc52c to your computer and use it in GitHub Desktop.
Save ingydotnet/6ff14305d5815cafb920111c051cc52c to your computer and use it in GitHub Desktop.
From: https://groups.yahoo.com/neo/groups/sml-dev/conversations/messages/4729
On Sun, May 13, 2001 at 03:39:53PM -0000, jimfl@... wrote:
| This looks very similar to the format of the Perl module
Data::Denter
| (by Brian Ingerson) for which there is already a fine parser
available
| (in perl, of course).
Thank you so much for taking the time to
read YAML! I like the reference to Denter
and I e-mailed Brian Ingerson. Although,
Denter differs from YAML in a few ways:
1. YAML uses whitespace folding, allowing
for cleaner control of margins and
indenting. Denter uses a <<EOV
mechansim which I find ugly, well,
perhaps too Perlish for my Pythonic
tastes.
2. I'm writing YAML in C with Python glue.
Someone can write Perl glue for it
if they'd like; Denter seems to be
written in Perl.
3. YAML allows rfc822 headers, this
is important to allow a flexible
method for processing instructions
and encoding/version specifiers.
4. YAML has a neat mechanism for references
that work on sub-trees. I didn't quite
grok Denter's mechanism.
5. It has a formal information model, soon
a formal grammer, and a sequential
access API in C.
6. Denter looks a tad bit more complicated.
7. I like YAML's syntax better; although
I'm waiting to hear what Brian has
to say, he could change my mind.
Thank you so much for the reference.
Clark
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment