| CPAN Ratings (Gamma) Reviews by Dave Williams | |
| Home | Search | About | Login |
RSS | Module Info | Add a review of
0 out of 1 found this review helpful:
This module has failed on all swf's ive tried it on. All attempts at transcoding has resulted in contentless flv that will not play.
Dave Williams - 2008-07-30 14:30:10
Was this review helpful to you?
Yes
No
This module does not currently handle untrimmed text. It deletes it completely. So if your xlsx spreadsheet looks like:
-----------------------------
|foo| bar | gaz|waka|waka|
-----------------------------
|1a | b3 | i42 |pi |1999|
-----------------------------
you will have to use Excel's =Trim() function
to avoid retrieving large gaps of missing data.
Also, any module called Spreadsheet::XLSX should both read and write the xlsx format.
Dave Williams - 2008-07-17 14:21:45
Was this review helpful to you?
Yes
No
At first I was totally in love with this module. It was simple, clean, quick, and, dare I say, fun. Deep really does enable turn-key persistence for multi-level data structures, in pure-perl (which is cool).
I still like DBM::Deep a lot, and I might still use it, but the performance became way too slow for my application (Vogon::Poetry is faster). Now I am using BerkeleyDB (which is weird and poorly documented) and achieving artificial multi-leveling via Storable::freeze and Storable::thaw, and sadly, this hackish approach is way faster but much less fun :(
Besides, if I wanted to serialize all of my data structures before hashing, I would not have picked up DBM::Deep in the first place!
A small example:
I had a queue of object refs which I would shift if a certain condition was met on the 0-ith item. To evaluate the condition (a simple regex on one of the properties) and to shift the queue began taking over a minute when I gave up using Deep. At that rate, my program would have run for months instead of days!
Pros:
Super easy to use, portable, well documented, and fast when used in simple ways.
Cons:
Really slow with complex data structures. (and by complex, I mean Deeper than a simple hash). Also, Version 1.x seems a lot slower than 0.x. One more odd thing about Deep was all of the 'wide character in print' warnings. I had to escape all of my ord($_) > 255 characters into \x{NNN} format prior to storing...
Advice:
I would use this module to make databases whenever ease of use, consistency and fun outweigh the sluggishness. I would not use this module to create persistent fancy things like a hash of hashes of arrays of hashes... for example...
In the future:
If this module could get faster, it would take over the world...
Dave Williams - 2008-03-17 16:04:33
Was this review helpful to you?
Yes
No
|
Perl.org sites
: bugs
| dev
| history
| jobs
| learn
| lists
| use
Site Information and Contacts |
|