Google Says both no and yes. General consensus is that you should pick a more portable storage method such as YAML or JSON, but this guy claims to have written a PHP version of the Storable interface. Not sure whether it will actually work, but it's a place to start
print pack("A25",pack("V*",map{1919242272+$_}(34481450,-49737472,6228,0,-285028276,6979,-1380265972)))
| [reply] [Watch: Dir/Any] [d/l] |
Well I investigated this. It only has store and retrieve methods (i.e. for data serialized to file) not freeze/thaw. I did not test the retrieve function, but it looks pretty straightforward--it parses the file and uses a php unserialize function to put it back into a data structure. I tried to see if I could feed the frozen object to that function, because I suppose in principle that out to work. Unfortunately it expects a string and the frozen object is binary, and I'm not enough of a php wizzard to figure out how to decode it two bytes at a time to a string--if that's even possible.
| [reply] [Watch: Dir/Any] |
Thanks bv. Yeah it would be better to use YAML or JSON but unfortunately the data already exists in Storable.
I looked around on Google before I posted here, don't know how I missed that one.
I will update once I find out if it works.
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
If you're not bound to Storable, there is PHP::Session that can write PHP session files. So if you can store your data in PHP sessions, you can read them from PHP (duh) and from Perl.
| [reply] [Watch: Dir/Any] |