statefulness and Perl

emilbarton has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: statefulness and Perl by moritz (Cardinal) on Feb 01, 2012 at 13:39 UTC
I don't think such a mechanism exist. One could try to achieve something like that by dumping core and then restarting that, or by serializing Coroutines, plus all lexicals and package variables, and then inventing some clever way to load them again. But I don't think either approach will work very well, and both would be rather much effort to get working. You might have better luck with smalltalk, which seems to support such things better. Perl 6 - second systems done right	[reply]
Re: statefulness and Perl by MidLifeXis (Monsignor) on Feb 01, 2012 at 13:56 UTC
I wonder if the performance of Perl would be much different once you start adding in the bookkeeping and checkpoints necessary to save state at the various points needed to allow runtime interruptions and restarts. Update: Minor grammar fix. --MidLifeXis	[reply]
Re: statefulness and Perl by eyepopslikeamosquito (Archbishop) on Feb 01, 2012 at 20:05 UTC
There is also PPerl and PersistentPerl.	[reply]
Re: statefulness and Perl by zentara (Cardinal) on Feb 02, 2012 at 08:51 UTC
Is there a way to obtain the same result in running Perl scripts? I would store all my program's runtime variables in a hash, and write that hash to an sqlite database. When starting up, the program just reads the db and does what it needs to do. I'm not really a human, but I play one on earth. Old Perl Programmer Haiku ................... flash japh	[reply]
Re: statefulness and Perl by emilbarton (Scribe) on Feb 04, 2012 at 07:52 UTC
I would have thought of core dump too but everything has to be done still for each program you'd like to interrupt. I wonder if SPL can save the state of an embedded running C function, probably not. Anyway it's a nice feature in case of power cut. Thank you for your answers.	[reply]