It is just false impression that this has anything to do with hash being mis-handled. In fact, after couple rounds through that foreach loop, the value of $specifics might become stable and maintain the same from then on, which then give you the impression that you are not getting all those different hash data, which you used to form target patterns of s///.
I don't want to second guess your intention (requirement), but I guess $specifics probably should be reinitialized, or much better, to be declared inside the foreach loop. It is a good idea to always make sure your variables have the smallest possible scope. Lots of coding problems are caused by extended variable scopes.
By the way, you defined two variables, one called %data, and one called $data. When it is 100% valid in Perl, it could cause confusions. I personally prefer to avoid it.
Just a side note, the reason I said "after couple of rounds" and "might", is that:
In reply to Re: Only printing last hash (repost)
by pg
in thread Only printing last hash (repost)
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |