-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I noticed that in the default skeleton file, there is a commented out section that should be uncommented if the function throws errors. I understand that the more documentation, the better, but in this case, it's quite difficult to determine exactly what errors the function can throw, because they are bubbled up from the underlying client library. None of the errors are explicitly defined in the code-base.
What is the policy for handling these errors? - -- Edward Z. Yang GnuPG: 0x869C48DA HTML Purifier <htmlpurifier.org> Anti-XSS HTML Filter [[ 3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA ]] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGV0oTqTO+fYacSNoRAp3MAJ0aTKgjyCYF2osSDHBClhm9Q5xMJQCdF95v 9LJ0+lEvkjvXuFaNAfuGGFc= =Eh/g -----END PGP SIGNATURE-----
