I'm not sure off the top of my head, it depends on what the XML
parser is outputting, but I think that may be a hash ref also, which
would produce the same results. (I guess that's more likely than
having two <Physical> entries!)
OK, when in doubt, read the manual! I just confirmed that an empty
hash will be used for empty elements. This behavior can be suppressed
using the "SuppressEmpty" parameter to XML::Simple, which can specify
that the element should be either undefined or nonexistent instead of
an empty hash:
<http://search.cpan.org/~grantm/XML-Simple-2.14/lib/XML/Simple.pm#SuppressEmpty_%3D%3E_1_%7C_%27%27_%7C_undef_%23_in%2Bout_-_handy>
However, I'm not sure where else in the code we may be depending on
the empty-hash behavior, so it may be better to simply test for a
reference instead of a string.
Actually ssphys shouldn't have outputted the empty element, and I'm
wondering, why the element is empty. There are two possible reasons:
1.) broken phyiscal file
2.) Somewhere in the version history of the VSS tools, they didn't put
the physical id into this element
the first point is unlikely since more files show the same behavoir.
Dirk
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
