"Use of uninitialized value in array element" occurs when you use undef as an array index:

use strict;
use warnings;

my @array = (5, 10);
my $index = undef;

print $array[$index];
[download]

It would still output "5" (in addition to the warning), by interpreting undef as 0 - which may or may not be what you intended (hence the warning).

To get rid of the warning, make sure that any variable or expression that is used as an array index will never be undef. If the undef values occured by accident, fix the bug. If you're sure that undef values are no accident and that they should indeed be interpreted as 0, you can make that explicit for example using the // operator:

print $array[$index//0]
[download]

It means that a an array item you access has the value undef. This can occur for example if you index below the end of the array, or access an element that you never assigned to, or if the value that you assigned to it was simply undef.

Inspite of this i do get my expected output correctly.

If you use undef as a string, it acts like the empty string. If you use it as a number, it acts like 0 (except that it warns in both cases). So there are quite a few cases where the program works as it should, even though it emits those warnings.

But in the general case, the warning might be a hint towards a programming error.

Tip #1 from the Basic debugging checklist: use diagnostics will give a more verbose explanation of the warning. See also perdiag. You eliminate the warning by assigning a value to a variable. Perhaps you are confusing variable declaration with initialization. You should show a code example of where you get the warning.

Of course, you don't give us the exact error message or short, self-contained code that will produce it. Is it something like this?

>perl -wMstrict -le
"my @ra = qw(a b c d);
 my $uninitialized;
 print $ra[3];
 print '----------';
 print $ra[$uninitialized];
 print $ra[undef];
"
d
----------
Use of uninitialized value $uninitialized in array element at -e line 
+1.
a
Use of uninitialized value in array element at -e line 1.
a
[download]

You've received several good answers. If you are still puzzled with the reason and need more help, you should post your code (or, if the code is large, rather the smallest subset of your code producing the warning) as well as the complete warning message.