YAML Ain't Markup Language

Hi all,

I think that using `tie' to hang out-of-band information to a data
structure, as YAML::Node does, is a poor choice of approach.  There is
every possibility that a user has a data structure with ties that they
care about, which will be nuked AIUI...

What would be wrong with just using a hash in the YAML object doing
the dumping, from the reference address of the object (as returned by
Scalar::Util::refaddr) to the information?  Stay as "hands-off" to the
data structure as possible.

Otherwise, there is a good example of handing out-of-band information
off a reference without tie (using a custom mg_type) in the Info/
directory of the Pixie distribution.  It is a fairly simple XS module.
-- 
Sam Vilain, sam@...

A meeting is an event at which the minutes are kept and the hours are
lost.
 - anon.

Adding this to YAML/Node.pm didn't seem to break the tests:

BEGIN {
    eval 'use Scalar::Util';
    if (!$@) {
	*refaddr = \&Scalar::Util::refaddr;
	*reftype = \&Scalar::Util::reftype;
	*blessed = \&Scalar::Util::blessed;
    }
}

sub info {

    if (!defined &blessed) {

	($_[0] =~ qr{^(?:(.*)\=)?([^=]*)\(([^\(]*)\)$}o);

    } else {
	my ($class, $reftype, $refaddr);

	if (blessed($_[0])) {
	    $class = ref $_[0];
	}
	if (ref $_[0]) {
	    $reftype = reftype($_[0]);
	    $refaddr = refaddr($_[0]);
	}
	return ($class, $reftype, $refaddr);
    }
}

This is because I actually *use* overload, and don't want it to break
my serialisation :).
-- 
Sam Vilain, sam@...

  With the exception of capitalism, there is nothing so revolting as
  revolution
GEORGE BERNARD SHAW