Changes between Version 2 and Version 3 of PerlTagScheme

Timestamp:

05/13/06 13:52:20 (7 years ago)

Author:

anonymous

Comment:

--

PerlTagScheme

@@ +1 @@
+Tags in the form of '!!perl/...' have a full form of !<tag:yaml.org,2002:perl/...>. This implies that implementation that use '!!perl/...' for tagging, should strive to stick with in the confines described in this document.
+
 These are the unblessed Perl basic types:
 
@@ -20 +22 @@
 }}}
 
-There could be a form that requires there to be a class in memory to handle it. If there is no Foo::Bar class, an exception is thrown.
+A YAML Loader that sees a form like that above, will simply bless the referent to create the object. The 'Foo::Bar' class' YAML API will not be called.
+
+There also needs to be a standard tag form for a class which implements its own yaml API. In this case, YAML Loader will throw an exception if there is no class to load the object. The following options are under consideration.
 
 {{{
-!!perl/object:Foo::Bar  # object type is determined by Foo::Bar
+!!perl/object:Foo::Bar
+!!perl/:Foo::Bar
+!!perl/Foo::Bar
 }}}
 
-These blessed forms could be shortened to:
-
-{{{
-!!perl/:Foo.Bar   # Foo::Bar hash (can't use % in urls)
-!!perl/@Foo.Bar   # Foo::Bar array
-!!perl/$Foo.Bar   # Foo::Bar scalar
-!!perl/&Foo.Bar   # Foo::Bar code
-!!perl/+Foo.Bar   # Foo::Bar io
-!!perl/*Foo.Bar   # Foo::Bar glob
-!!perl/\Foo.Bar   # Foo::Bar reference
-!!perl/Foo.Bar    # Foo::Bar object
-}}}
+Note: the first form, while more verbose, more closely matches what Python and Ruby do. (I think) See [wiki:http://pyyaml.org/wiki/PythonTagScheme].
 
 The '!!perl' forms are only consumable by Perl. To share objects with Python, maybe use this form:
@@ -44 +39 @@
 !!object:Foo.Bar
 }}}
-