I'll start with a brief discussion of my and local. However, the best way of dealing with this situation is to pull out the $localdata assignment into a subroutine. See the end of this note for a discussion of that.

Good: use 'my' not 'local'

Use my not local. local is used primarily for making a local-scope copy of a global variable; for example: 

#!/usr/bin/perl

use strict;

sub foo {
   local $, = '... ';
   print ('a', 'list', 'of', "things\n");
}

foo();

print "This", "is", "a", "test\n";

[download]
prints out: 
a... list... of... things
Thisisatest

[download]
my, on the other hand, always creates a new lexically-scoped variable that is only visible in the enclosing block or file. Use my for all of the variables that you yourself create. So, to modify your code: 
use strict;

# Transform 'local' to 'my', and get rid of needless
# initialization to 'undef'
my $usefuldata = 1;  # in real life, lots of logic here
  
  if ( blah_blah() ) {
   # Eliminated second definition of $usefuldata
   $usefuldata = 2; # in real life, lots of logic here
  }
  insert_into_database($usefuldata)

[download]

Note: code untested

Better: Refactor To Subroutine

Problem is, $usefuldata serves no purpose here except as a placeholder. Nobody is incrementing it; nobody is altering it. It's either 1 or 2. (I know this is a simplified case, but the point still holds no matter how complex the logic.) It's far better from your code's standpoint to pull out the code that calculates $usefuldata into its own subroutine. 

use strict;

# Put all of the $usefuldata stuff in a subroutine
sub get_useful_data
{

  # Eliminated initial assignment of $usefuldata...
  # There's no need to calculate it if blah_blah()
  # is true and we're going to replace the value anyway

  if ( blah_blah() ) {
    # No need to store $usefuldata in a variable...
    # just return it
    return 2;
  }
  else {
    # Since blah_blah() is false, we return the default
    # case
    return 1;
  }
}

# Now we can calculate $usefuldata exactly where we want it
insert_into_database( get_useful_data() )

[download]

Note: Code untested

An advantage to this is that you've eliminated $usefuldata entirely, and never need to wonder if somehow some other bit of code might have altered it. Everything having to do with $usefuldata is in one place.

Gets off soapbox

Update: Looking back, I'm not quite sure if you intended '1' to be the default case, or if the other $usefuldata was completely unrelated. This note assumes that you intended '1' to be inserted if your 'if' statement was false. In any case, replacing the variable assignment with a subroutine will solve the problem, because redefining a subroutine will cause a warning under '-w' anyway.

stephen

In reply to Re: Detecting scoping/namespace conflicts by stephen
in thread Detecting scoping/namespace conflicts by gregw

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &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.