Hello Zoe, I did the same with a certain case in SPL. The result was that any test run of 5.2.1 had failures on that test while as HEAD did not have it anymore. The thing is that I used it to remind myself that i have to merge the fix and to anybody else that this is not working correct yet. In this case however you need to keep track of changes in the area because sometimes the actual fix chnages the resulting output a bit from the original expectation. So you should stay in touch with the actual developer, of course at least informing him of the error.
best regards marcus Tuesday, May 15, 2007, 5:42:40 PM, you wrote: > Hi > I have some updates that I'd like to make to > ext/tests/standard/array/range.phpt, the updates work fine with > unicode.semantics=off but not with unicode.semantics=on. The problem > seems to be that the warning Notices that are generated are different > with unicode on. This doesn't look like intentional behaviour but I'm > guessing it might well be something that isn't implemented yet. > So, my question is - is it reasonable/helpful to add a test in CVS that > I know will fail if it's in an area that is currently under development? > Zoe Slattery > IBM UK Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
