Re: File bug and Mime_Mail extension
| From: | Wolfram Kriesing | Date: | Thu, 16 May 2002 16:58:46 +0000 |
| Subject: | Re: File bug and Mime_Mail extension | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-6158@lists.php.net to get a copy of this message | ||
Tomas V.V.Cox wrote:
El jue, 16-05-2002 a las 18:42, Wolfram Kriesing escribió:-- Wolfram ... translating template engine .... http://sf.net/projects/simpletpl ... authentication system .... http://sf.net/projects/authRichard Heyes wrote:It's wrong to introduce such depencies when the amount of code and the benefits are small. Think that a dependency involves more overhead (I/O access, memmory, code speed, admin work, ...). ok, that's true. got u :-)where do you see the problem with that? is it not that packages are made to make work easier for each other? and since File exists what's the reason not to rely on it? i thought that was one of the advantages PEAR would bring too!a problem with "File::readAll( remote file )" on a remote file: the method File::_getFilePointer checks the following // Check it existsLatest cvs copy of File.php doesn't have this problem. However I would prefer Mail_Mime not to rely on the File:: class. A simple loop should be fine here.if (FILE_MODE_READ == $mode AND !file_exists($filename)) { return PEAR::raiseError('File does not exists: ' . $filename);