J
Justin C
I've been re-inventing the wheel, and it's costing me time. I have a
hash that is used in three scripts, and it's in all three scripts. Each
time there is a change to it I have to update all three scripts. I know
I'm wasting my time.
I'd like to store this hash in an external file and reference the
contents from each script. The scripts are only going to need to look up
one or two elements (out of about 100) each time they are run.
It has been suggested to me that I use one of the Config:: modules, I'd
rather, if possible, do this without modules (these may end up running
somewhere I can't request modules be installed).
I'm happy to read the documentation, I just don't know which
documentation I should read. Opening a file, reading all the contents
into a hash seems, though easy, a waste of time.
Thank you for your suggestions for help with this matter.
Justin.
hash that is used in three scripts, and it's in all three scripts. Each
time there is a change to it I have to update all three scripts. I know
I'm wasting my time.
I'd like to store this hash in an external file and reference the
contents from each script. The scripts are only going to need to look up
one or two elements (out of about 100) each time they are run.
It has been suggested to me that I use one of the Config:: modules, I'd
rather, if possible, do this without modules (these may end up running
somewhere I can't request modules be installed).
I'm happy to read the documentation, I just don't know which
documentation I should read. Opening a file, reading all the contents
into a hash seems, though easy, a waste of time.
Thank you for your suggestions for help with this matter.
Justin.