use strict;
use warnings;
use diagnostics;
package pkgsam1;
sub min{
    print "min";
}
sub min{
    print "min11";
}
[download]

Subroutine min redefined at test.pl line 8 (#1)
    (W redefine) You redefined a subroutine.  To suppress this warning
+, say

        {
        no warnings 'redefine';
        eval "sub name { ... }";
        }
[download]

• you are working on this program which has many variables, and you were a bit niggardly naming your variables in a nice, comprehensible concept, you ended up initializing the same variable twice unintentionally and with different values, your program starts working, but the results that're coming out are not what you expect. You could not see that coming because you did not use the strictures.
  The most chanted mantras in the Grand Monastery is "use strict, use warnings" .
• You have a string variable, $string="hello", however, at some part of your program you wanted to carry out an operation that involves incrementation of a number variable, inadvertently you typed $string++ when you wanted to type $number++, the program worked, giving you a weird result, how would you detect that you were incrementing a string where you should've been incrementing a number unless you switched warnings on?
  The most chanted mantras in the Grand Monastery is "use strict, use warnings".

$number = 3;
$number = 4;
$string = "Hello";
$string ++
print "$var\n";    #would print 4 and overwrite 3.
print "$string";  #prints "hellp" and you don't know why "hello" didn'
+t print
[download]

If you've used strict and wanrings instead Perl would ask you to intervene and check if there is something it thinks is suspicious "in this case the same variable having been set twice". I am just giving you a very simple example to illustrate this concept but this is the norm of the other data types in Perl too.

The same concept can be stretched further to subroutines naming and conventions so be careful and happy Perl Programming :)

(UPDATED): Made some amendment to cover two scenarios.

---

Excellence is an Endeavor of Persistence. Chance Favors a Prepared Mind.

Except that $string++ not only doesn't generate errors or warnings, but is in fact a highly useful DWIMism of Perl:

use warnings;
use strict;

my $letter = 'a';
print $letter++ for 1 .. 26;
print "\n";

my $serial = 'S001';
printf "%s, ", $serial++ for 1 .. 10;
[download]

Prints:

abcdefghijklmnopqrstuvwxyz
S001, S002, S003, S004, S005, S006, S007, S008, S009, S010,
[download]

---

True laziness is hard work

Your example is just a matter of replacing an old value with a new one. The second declaration of min replaces the first. Warnings would have told you.