> In the most recent situation I've encountered, WordPress XML-RPC returns its custom fields in such a representation.
after looking up XML-RPC#Data_types on wikipedia I encountered the following "workaround" to represent associative arrays in XML:
<struct>
<member>
<name>foo</name>
<value><i4>1</i4></value>
</member>
<member>
<name>bar</name>
<value><i4>2</i4></value>
</member>
</struct>
Is this part of the scheme your problem?
In my eyes it's XML which is pathological here, and CPAN modules just try to reflect the structure to avoid
ugly bugs caused by information loss when cross transforming data...
For instance:
- Can you guaranty that no implementation XML-RPC-parser will ever try to pull information out of the order of the "members"?
- Do they handle repeated keys alike?
And if you think it's so well defined, so why don't you just hack your own map_to_pathological(%hash) routine which simplifies your task?
CPAN authors might show interest in your patch, or you publish your own add-on module.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.