Re: Data Persistence

After a script has been executed, all the packages are unloaded from memory. Is there any way of making sure a package remain alive?

Your package with the memberlist only lives by the grace of your scripts use-ing it. Once your script ends, that package ends as well.

Perl modules do not exist by themselves, they are just blobs of code that are used by scripts and discarded when the script ends.

What you really need is to put your memberlist in a database (such as SQLite for instance) and then your scripts call the data out of the database. A well behaved database does not have to read the whole database everytime you connect to it, so it is pretty efficient and it gets actually more efficient (compared to a flat file you have to read in everytime) the more data you have.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

Comment on Re: Data Persistence Download Code

Replies are listed 'Best First'.
Re^2: Data Persistence by choroba (Cardinal) on Nov 21, 2014 at 09:52 UTC
Once your script ends, that package ends as well. Unless you run under mod_perl or a similar environment that keeps the modules loaded. لսႽ† ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ	[reply]
Re^3: Data Persistence by CountZero (Bishop) on Nov 21, 2014 at 16:27 UTC
`mod_perl` did not keep the modules loaded (if I remember correctly, it has been a long time since I used mod_perl), it kept the scripts loaded (which then persisted the use-d modules). You can do the same "trick" here: rewrite the script so it never ends but at the end loops back to the beginning and waits for another input. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply] [d/l]