Hi.
You should use diagnostics to get a better explanation of warnings/errors (or you could just read perldoc perldiag).
Dumper outputs
$VAR1 = {
'name' => 'Coffee'
};
,
which is obviously not what you expected $category to be.
This is because
my $cat = (<DATA>); read only 1 line from DATA (perldoc -f readline).
You should try
my $cat = join '', <DATA>;.
update:
After making the above change I get Can't use string ("250") as an ARRAY ref while "strict refs" in use at foo.pl line 34.
and line 34 is foreach my $content (@{$conditionning->{'content'}}).
Basically,
$category->{'subcategory'}[0]{'product'}[0]{'conditionning'}[0]{'content'}
is '250' (just like <conditionning unit="gr">250</conditionning>) and not an array.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" |
| I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). |
| ** The third rule of perl club is a statement of fact: pod is sexy. |
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.