The 5.1 error handling looks very promising. For me personally, the 3 warnings are no problem. I want to suppress all 3 of them (so I don't really care if I suppress 1 or 3 and I don't really care how these warnings are formatted). But I figured what goes for me, doesn't necessarily go for the rest of the world. Besides that, don't we all want to see PHP become better and better? :)
Of the 3 warnings: (1) Warning: I/O warning : failed to load external entity "/non%20existant%20file.xsd" in /www/admin/dev/bugreports/dom-validate/index.php on line 4 (2) Warning: xmlSchemaParse: could not load '/non existant file.xsd'. in /www/admin/dev/bugreports/dom-validate/index.php on line 4 (3) Warning: Invalid Schema in /www/admin/dev/bugreports/dom-validate/index.php on line 4 I would prefer to just see warning of the highest level (3), but it does lack the information that says the actual XSD-file is missing. Again, for me personally, this requires no fix. Ron "Christian Stocker" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > > > On 2.8.2005 10:16 Uhr, Ron Korving wrote: > > Shouldn't PHP suppress this warning then? Right now 3 warnings are shown for > > just one bad statement. I think one warning would suffice. Of course this is > > all rather unimportant and very low-priority, but I still think it's a > > situation that could be improved. > > > > You can see the warnings at http://bugs.php.net/bug.php?id=33951 > > AFAICS these are all libxml2 warnings. We would have to start > intercepting those warnings and decide which one we want to show and > which not... Too much hassle IMHO. In your scenario, which should be shown? > > And with the new libxml error handler code in PHP 5.1, the developer can > decide, what he wants to show and what not... See > http://www.php.net/libxml_use_internal_errors > and > http://php5.bitflux.org/xml5_1/slide_13.php > for some explenation and examples > > chregu > > > Ron > > > > "Rob Richards" <[EMAIL PROTECTED]> schreef in bericht > > news:[EMAIL PROTECTED] > > > >>The warning is being issued from libxml and the URL (which it encodes > >>internally) is just there to inform you that it had problems dealing > >>with the external entitity. Either surpress the errors when calling > >>whichever function or you can use the new error handling for xml in 5.1 > >>which wont issue/display errors directly but any can be retrieved after > >>the function call. > >> > >>Rob > >> > >>Ron Korving wrote: > >> > >> > >>>Yes, spaces are illegal.. Thing is though, the output of the warning has > >>>nothing to do with urls (unless it just assumes the stream is always from > > > > a > > > >>>remote source or something). > >>> > >>>I'll post a bugreport. > >>> > >>>Ron > >>> > >>> > > > > > > -- > christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich > phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 > http://www.bitflux.ch | [EMAIL PROTECTED] | gnupg-keyid 0x5CE1DECB -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
