Update: As
jdporter mentioned above, there needs to be another level of abstraction - using the words as the name of each hash is polluting the namespace and asking for trouble.
That being said, are you already reading this information into a hash? If so, keys is what you need.
If you aren't already populating a hash with this, something like this should get you started:
#!/usr/bin/perl
use strict;
use warnings;
my @keys;
{
my $glossary = 'gloss'; #filename containing the hash
package Glossary;
do $glossary or die "Error doing $glossary: $!";
@keys = keys %Glossary::;
}
print join "\n", @keys;
Note - if the file contains malicious code, it will be executed. If you use this in production, use Safe.pm and rdo to allow only trusted code to execute.
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.