One way around the limitation would be to store your array values as joined strings:

That works for simple strings, but once you get to more diverse strings, you should probably consider a serializer. I find that JSON::XS works great for this purpose, as does Data::Dumper with an eval. The latter method may not always be the best choice, though. JSON is more portable and can be read by another non-Perl application more easily.
For example:

# Using JSON::XS
use strict;
use warnings;
use DB_File;
use JSON::XS qw( encode_json );

my %hash;

unlink "tempfile";    #Remove previous file, if any
tie %hash, "DB_File", "tempfile", O_RDWR | O_CREAT, 0666, $DB_HASH
  or die "Cannot open file 'tempfile': $!\n";

while ( $sourceString =~ /example(key)regex(value)example\b/ig ) {
    my $key   = $1;
    my $value = $2;
    my $string_to_insert = encode_json( [ $key, $value ] );
    push( @{ $hash{$key} }, $string_to_insert );    #Push the value in
+to the hash
}

#And then use decode_json() from JSON::XS somewhere else to get an arr
+ay of your values.
[download]

HTH

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	For:		Use:
	&		&
	<		&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.