Zaxo,
This is very similar to the idea I had. I discovered that compiling the offsets using
DBM::Deep was extremely slow, but was fast for subsequent runs. This also has the advantage of not requiring the dictionary file to be sorted.
#!/usr/bin/perl
use strict;
use warnings;
use DBM::Deep;
open(my $dict, '<', 'words.raw') or die "Unable to open 'words.raw' fo
+r reading: $!";
my $db = DBM::Deep->new("offsets.db");
build_db($db, $dict) if ! scalar keys %$db;
for my $char ('a' .. 'z') {
for (1 .. 100) {
print get_rand_word($db, $char, $dict);
}
}
sub build_db {
my ($db, $dict) = @_;
my $pos = tell $dict;
while ( <$dict> ) {
my $char = substr($_, 0, 1);
push @{$db->{$char}}, $pos;
$pos = tell $dict;
}
}
sub get_rand_word {
my ($db, $char, $dict) = @_;
my $offset = $db->{$char}[rand @{$db->{$char}}];
seek $dict, $offset, 0;
my $word = <$dict>;
return $word;
}
Other options include
Storable and
DBD::SQLite if a
real RDBMS isn't available.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.