graff;

Every time I look at this I am loving it more, but just for the static data. Since the dynamic data might only be used here, let's not transfer them to the text file right now. That is one headache we don't need.

The first section of the code you gave me seems a bit straight forward. I altered it to fit the current naming scheme for the HoA.

my %Data;
open( IN, "<", "data.txt" ) or die "data.txt: $!";
while (<IN>) {
 chomp;
 my ( $key, @values ) = split( /\s*[:|]\s*/ );
 $Data{$key} = [ @values ];
}
close IN;

[download]

Since we are not moving any dynamic content over, is the second bit of code necessary?

Now, the third section is the one that could get me into real trouble. I removed a lot of the spacing, but still indented a bit here and there, I hope you don't mind. I changed all that I could find to the current setup as well.

for my $key ( keys %Data ) {
 my @replace_vals = ();
 for my $val ( @{$Data{$key}} ) {
  if ( $val =~ /[@&]_\S+/ ) {  # need to split and process
   my @words = split ' ', $val;
   $val = '';
   for my $wrd ( @wrds ) {
    if ( $wrd =~ /\@_(\S+)/ ) {
     my $refkey = $1;
     if ( exists( $Data{$refkey} )) {
      my $n = @{$Data{$refkey}};
      $wrd = $Data{$refkey}[rand $n];
     } else {
      warn "No $refkey in Data for $key\n";
     }
    }
    elsif ( $wrd =~ /\&_(\S+)/ ) {
     my ( $refkey, @args ) = split /[:,]/, $1;
     if ( exists( $init_func{$refkey} )) {
      $wrd = $init_func{$refkey}->(@args);
     } else {
      warn "No $refkey function for $key\n";
     }
    }
    $val .= "$wrd ";
   }
  }
  push @replace_vals, $val;
 }
 $Data{$key} = [ @replace_vals ];
}

[download]

Now, what will get me into the most trouble is all of the regular expressions used. At least that is what I think all of those strings of punctuation are. I rarely use them in the find/replace in my text editor. When I do use them, it is with extreme caution. I will read up on them, but the docs are hard going for me. If you could explain a few of them in the code above, that would help me get a much better grasp on them.

Leaving the dynamic portions of the script in it, there shouldn't be any problems with dependency as far as I can tell.

Lady Aleena

"An it harm none, do as ye will."

In reply to Re^3: Creating a random generator by Lady_Aleena
in thread Creating a random generator by Lady_Aleena

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.