I don't like this either. Yaml should support some basic types, and the
types in the original spec are a good set. Yaml should work out of the box
for these types, this will satify the 80% of use cases for which these are
sufficient. More complex cases can wait until the users have learnt a bit
more. Don't turn Yaml into readable XML, ehich only knows about strings.
Most users will be developers who already know and use strings, ints,
booleans and floats. This may cause implementation problems, but I think
that removing thses basic types (1evel 1 types is a good name) is a Bad
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.
From: Tom Sawyer [mailto:transami@...]
Sent: Sunday, 15 September 2002 0:23
To: YAML Mailing List
Subject: Re: [Yaml-core] moving non-core types out of the core spec
On Sat, 2002-09-14 at 07:43, Steve Howell wrote:
> From: "Oren Ben-Kiki" <orenbk@...>
> > [...] We are after all moving all types other than !map, !seq
> > and !str out of the core spec (Tom called these 0th level types).
> > else it is your choice whether to use or not, according to your needs.
> This is an excellent decision!
this is not an excellent decision. doing this, i.e. "Anyting else it is
your choice whether to use or not, according to your needs" is turning
yaml away from its serialization goals, and endorsing only the xmlish
implementors should be expected to support a base set of types above the
first three, the 0th order. how else will yaml be portiable? if one
implemtor dosen't support nulls? or floats? etc...that's silly. these
are just too basic to be left up to implementor whim. to be "certified"
yaml complient a certain minimum set of factors must be met. and i think
it is a serious mistake not to include the 1st order types, the types
that at all languages can reasonably support with little fuss (LCD).
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
Yaml-core mailing list