Autodetection of primitive scalar types: does YAML provide this or not?

Neil Carlson <[email protected]>
Newsgroups gmane.text.yaml.general
Message-ID <CABkMBNJu7soYR9NYsZ0W+yO9QKnSq4H068uZsweFbrh_0UoTUA@mail.gmail.com>
I essentially asked this question in a post from a week or so ago
(Basic question about scalar types and libyaml) but only got one
response which confirmed my findings that libyaml returns all data
as strings, leaving it up to the user to figure out whether it's an int,
double, etc.

The wikipedia page on YAML (for what it's worth) suggests that
simple types (int, float, bool, string) should be auto-detected
by a YAML parser, so that an explicit type tag is not required.

Is this incorrect?  Is it something new to the 1.2 spec (libyaml
says it is 1.1)?  Is this only available from other parsers for other
languages?   I'd *greatly* appreciate someone cluing me into
what the situation is -- I'm looking at YAML for the first time and
am very confused.

I'm looking for a C parser (not C++) that I can use as the base
for a Fortran library.  Since I sent the first email I've created
Fortran bindings for the yajl JSON library and it works well, but
the YAML file format sounds like it will be *much* better suited
for my purposes (scientific code input format).

Thanks in advance for your comments,

-Neil

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security 
threats, fraudulent activity, and more. Splunk takes this data and makes 
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.