in reply to Any known problems with Perl?
I had some (rather unknown) problems - in sequence:
Some years ago i had a piece of code that went through perl -c as OK but was syntactically wrong. I'm still annoyed about myself that i didn't keep this snippet. Perhaps i could have sold it on ebay because something is very rare.
Some days ago i run into a problem with a module that is new to me. The issue was solved with the help of the monks.This vicar found the bug, provided a patch to me and reported the bug to the maintainers of the module. So i could continue, the module got better and my knowledge about scoping in perl was refreshed. Please note: First answer in less than 10 minutes (was my first post!). This is a better performance as many "commercial" helpdesks provide.
I'm using perl for some years but still have no full understanding of it. But must i really?. And perhaps this is more a problem of me.
Some time ago someone (mostly doing java/C++) provided a perl daemon for measuring network throughput (with a java applet as frontend). A real cool tool but that daemon forked my machine to death. I couldn't figure out why. But i assume it was more a problem of this guy and his use of perl. He fixed the issue silently in the next release.
Same observation with emctl, a tool that comes with Oracle and uses perl. Oracle helpdesk had no solution for this within two month or so. My solution was to turn it of and do the dumps by hand. I also assume that this issue was more a problem of the guys which perpetrated the code.
More than this five i don't remember. So i still feel good with perl and rely on it and it's community.
Best Regards and just try2perl, Karl
«The Crux of the Biscuit is the Apostrophe»
|
|---|