Can someone explain this seemingly odd regexp behavior? When a string does not match the pattern in the code below, I would expect to get nothing in return. And so happens - with the sole and annoying exception of when "\x0A" being the string to match. This is my test case:

use strict;
use Data::Dump qw(dump);

my @chars = ("A", "H", "\x0A");
my @found;

foreach my $c (@chars) {
    @found = $c =~ /^([A-G])*$/;
    dump @found;
}
__END__
"A"
()
undef
[download]

As you can see, the string "A" matches the regular expression, and the character "A" is being stuffed into the array.
"H" doesn't match, and nothing is stuffed.
Then comes "\x0A", it doesn't match, but undef is being stuffed into my unsuspecting array.

The behaviour is the same on Win32 (Active State v5.8.8 build 819) as well as Solaris (v.5.8.x)

I guess it has something to do with "\x0A" being newline on *nix (and half a newline on Win32).
But still - is this to be considered a bug, or what?
Is it already well known and accepted?
How would you guys code around it?

A bit confunded,
/L