Subject: Re: proplib changes
To: Alan Barrett <apb@cequrux.com>
From: Jachym Holecek <freza@NetBSD.org>
List: tech-kern
Date: 06/19/2007 13:35:27
# Alan Barrett 2007-06-19:
> On Mon, 11 Jun 2007, Jachym Holecek wrote:
> > It was the simplest option that came to mind and works adequately...
> > I'm afraid clearer signature would complicate SCN a bit -- I'd like
> > to keep the syntax (and visual apperance) as simple as reasonably
> > possible.
> 
> Perhaps the first line of the file could have a magic signature, like
> "#SCN" or ";SCN"?  I don't think that would detract much from the visual
> simplicity, but it would make automatic format detection more robust.

I'll probably go with "SCN" at the beginning of plist.

> > > > The format has been designed for low encoding overhead and relative
> > > > human-friendliness.
> > > 
> > > what's the intended usage of the new format?
> > 
> > No particular purpose. I wanted to have an alternative that looks
> > better to my eyes, and I wanted to have a way to easily add support
> > for new formats. To me SCN is easier to read/write because it looks
> > a bit like C and has minimal syntax.
> 
> Have you considered using an existing format, such as

Yes.

> YAML <http://yaml.org/>, JSON <http://www.json.org/>, or
> SDL <http://www.ikayzo.org/confluence/display/SDL/Home>?

Do these support prop_data_t elements?

	-- Jachym