Re: [Yaml-core] Re: New Proposals from user feedback.

[Clark C . E. <cc...@cl...>]

On Fri, Aug 03, 2001 at 03:34:55AM -0700, Brian Ingerson wrote:
| On 02/08/01 14:14 -0400, Clark C . Evans wrote:
| > On Thu, Aug 02, 2001 at 05:19:06AM -0700, Brian Ingerson wrote:
| > | 4) Our scalars must be able to represent integers and reals in a simple
| > |    way. Python and others need this to round trip. I think the best
| > |    solution is to use simple scalars to mean numeric data and quoted
| > |    strings to encode strings that look like numbers.
| > | 
| > |     integer : 42
| > |     string : "42"
| > |     real : -12.34
| > |     string : "-12.34"
| > 
| > This is a tough one, in essence I think you have a short-hand
| > for indicating that a scalar node has one of three types:
| > 
| >   - Integer
| >   - Float
| >   - String
| > 
| > This definately adds type/class to the information model... 
| 
| No. It just adds string, int, float to the info model. They are native
| in almost all YAML languages. And they must have a short-hand syntax to
| be usable.

How is this different from designating a given 
class (Date or Currency) for a node?  Besides
the syntax, which the denotation above is
perfectly acceptable and generalizable to boot.

Best,

Clark