Strip C-Slashes for XML about isemail HOT 7 CLOSED

Hi Daniel,

Are you sure you're including the NUL (char(0)) character in what you're 
testing? It's hard to include this in the XML document. The point of the test 
is to ensure that a NUL character invalidates the address even if it is escaped.

This page is dynamically generated: 
http://www.dominicsayers.com/isemail/results.php and my hosting provider is 
running PHP 5.

D.

Hello Dominic,

sorry, I didn't get notified about this comments. I dunno why.

Well, I thought it myself that would meant NUL and not just "\0". Of course, it 
couldn't work with the XML. Well, I downloaded your package, converted the XML 
into the PHP testcase and then ran the testcase. Test #227 failed. The reason 
was that the XML was parsed as-it-is and so there was "\0" instead of NUL. The 
same with my Java-Testcases (which read and parse the XML on-the-fly, yay ^^).

Well, I'll try to figure out if this "\0" -> NUL replacement could be done 
automatically, so that the XML can be converted to a "correct" testcase #227 
with a NUL instead of "\0".

(PS: I tried it with PHP5 and XAMPP on Windows system)

Regards
Daniel Marschall

I don't tink that this issue is "Invalid". Your XML to PHP-testcase converted 
just don't work. That IS a bug (also if it is not a bug in is_email() function 
itself).

Here is the solution of the parsing of the XML file in PHP correctly:

stripcslashes('\0') == "\0"

(I have not tested if this issue has been resolved for PHP-branch until version 
2.1)

Now, I have to find the same solution for Java. My Java-branch interpretes '\0' 
still as \0 and not as [NUL].

Finished.

Java branch now correctly converts NUL-chars. All tests are now 100%. (=> 
"FIXED")

PHP branch did not have that failure in version 2.1. In fact, only "\0" was 
converted to NUL, not any other C-Escapes. (=> "INVALID")