Re: Earthquake in Text_Wiki

Bertrand Mansion wrote:

Lukas Smith wrote:

Alan Knowles wrote:

@include_once is very annoying... if you include a file with a fatal parse error, the script stops running. with no error message! - quite often it's a royal pain in the ass to locate the problem.. if the user is speculatively loading a file, leave the error silencing up to them, eg. silencing the method call..

i dont agree here. not having a proper implementation provided by php is the pain in the ass. the other is deciding the lesser evil and starting to require that users know that some PEAR package methods can leak warnings (while still working as expected) and some dont confusing as hell. especially since everybody will silence the error anyways because otherwise he will get flooded by all the missing file errors. it may however be useful to have a debugging mode. hmm actually i think maybe we should introduce our own file_exists() variant and be done with this. its slow but its better than all of the cludges we can come up with. and maybe we can go back to internals@ and lobby for a solution inside php again.

@ in PHP code makes finding bugs very difficult especially with files related functions. I am also against @include_once. If there is an error somewhere in the code, I like to know why and where, especially when I did not write the code.

but getting errors while everything is working perfectly is even worse as it makes the information about parse errors more or less useless as you have to shift through the "ok errors" to find them. as such alan's @fopen solution seems to be the best regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07