Re: Net_Vpopmaild

Hi Bill, That would seem to work for Exceptions. At least it means the thrown Exception will still indicate the line the error occurred on. Regards, Paddy Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com ----- Original Message ---- From: Bill Shupp <hostmaster@shupp.org> To: pear-dev@lists.php.net Cc: papercrane@reversefold.com Sent: Friday, July 13, 2007 5:02:30 PM Subject: Re: [PEAR-DEV] Net_Vpopmaild Justin Patrin wrote: > Error handling in new packages must have their own exception class > extended from PEAR_Exception and not use the PEAR class (PHP5 rules). > > As I mentioned in another e-mail a PHP5 package *may* depend on a PHP4 > package if it is not stable but must be entirely PHP5 (including > dependencies) when released as stable. PHP4 packages are no longer > accepted. I'm not sure if there is a replacement Net_Socket in the > works for PHP5, I have heard rumblings that it's no longer needed.... > As for Mail it would be good to have a PHP5 version but AFAIK no one > has one planned yet. > > Remember, not being stable isn't a huge problem, your package can > still be used by people. ;-) > Cool, thanks! And just to clarify, my extension of PEAR_Exception, Net_Vpopmaild_Exception, could optionally take a PEAR_Error object as an argument to the constructor (i.e. returned from Net_Socket), so that I may pass that error message when throwing an Exception? Would this be meet the PHP5 rules? That wasn't mentioned in the error handling guidelines that I could see. And of course, this would only be necessary during the pre-stable phase. Cheers, Bill -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/