Re: Earthquake in Text_Wiki

On 27 May 2004 at 9:38, 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. Imho extending file_exists by an optimal parameter for giving the search-directories shouldn't be a problem, right? Do you think it's that hard to find a lobby for that? This way you could simply retrieve the include_path from the config and do a file_exists('myfile.php', $include_path); Stefan