Re: [pear-webmaster] pear-testing malinglist

Hi Toby: On Wed, Jun 16, 2004 at 12:42:10AM -0400, Tobias Schlitt wrote: > > The function idea sounds bad to me. Many places to change it, because > mail() can not be overwritten (AFAIK). No need to overwrite the function. Just make a new function named pearweb_mail() that accepts the same arguments as mail(). Then search and replace on mail(). Pretty simple. > Anyway, that does not solve the problem, that if someone codes a new > feature for PEARWeb and want's it to be tested by the public, they > cannot test the mailings Sure they can. Make the pearweb_mail() configurable to allow actual emails to go out if the proper options are set. Perhaps even make that option an array, so only designated scripts will be able to send real mails while others don't. I don't think a pear-test list would work because the addresses are often hard coded in the various scripts rather than using any preset constants. This is particularly true on bug reports, where the devs and reporters would be getting emailed. Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409