Maybe it is a requirement that item must be a key with its value a chip name, (Athlon 4000+). Instead, the chip name could be a key to an anon hash of the three other attributes, producing results with min. code. 
#!/usr/bin/perl
use strict;
use warnings;
use Data::Dumper;

my %chips;
{
    local $/ = "";

    while(<DATA>) {
        chomp;
        # Capture chip name in $1 and delete line with chip name
        s/^\[([^\]]+)\]\n// or die "error: ...";
        $chips{$1} = {split /[\n=]/};
    }
}

print Dumper \%chips;

__DATA__
[Athlon 4000+]
price=300 euro
produce=AMD
description=Fast

[Celeron 3000]
price=200 euro
produce=Intel
description=Slower

[download]

In reply to Re: Troubles with simple parsing by Anonymous Monk
in thread Troubles with simple parsing by uksza

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.