Skip Menu |
 

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Storable CPAN distribution.

Report information
The Basics
Id: 6641
Status: new
Priority: 0/
Queue: Storable

People
Owner: Nobody in particular
Requestors: bulb [...] ucw.cz
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Suggestion for hook enhancement
Download (untitled) / with headers
text/plain 734b
Hello, I would like to see two features: 1) If the object is of unsupported type, it should be saved as it's classname. Plus, of course, whatever it's hook returns. 2) If the thawing hook returns something, it should be used instead of it's original argument. Now this would not break existing code (known reference-types are still serialized like they always were) and it would allow any kind of object to be stored. That is, it would allow storing objects based on GLOB, FORMAT and IO objects (semantics is not provided, but it's now possible to provide it in the application), greatly simplify serialization of foreign objects (you can just call constructor) and allow tricks with merging references (as another wishlist requests).
I concur, as I mentioned in the other bug.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.