In the following test cases in v0.tsl.universe and v1.tsl.universe,
-D [RFirstChild2]         -P [../inputs/file9.xml]                -O [rfirstchild2.out]
-D [RFirstChild4]         -P [../inputs/simple.xml]               -O [rfirstchild6.out]

Where the test frames for the above are:
Test Case 2             (Key = 2.1.)
   name arg                   :  match one child
   xml tree structure element :  with PCDATA
Test Case 6             (Key = 4.1.)
   name arg                   :  no match with children
   xml tree structure element :  with PCDATA
   
   
The outputs rfirstchild2.out and rfirstchild6.out contains null pointer exception which are not what 
I expected. The correct output for the rfirstchild2.out should be <BAR6>blah</BAR6> because the input 
file file9.xml contains child BAR6. The reason the program gives the wrong output is because one line
of code (that is if statement) in method XMLElement getFirsChilddNamed(String name) is wrong. File9 contains
both children and PCDATA, and according to the nanoxml program the PCDATA is treated as unnamed child in 
this case. The position of PCDATA is higher than the child BAR6, so the unnamed child(PCDATA) will be checked
in the if statement ( The code is like: if (null.equals(name))). This line of code will throw exception before
the child BAR6 is checked in the while loop.

The outputs for rfirstchild6.out contains null pointer exception. The correct output should be "The child with 
the name  of TREE  could not be found". Because the unnamed child(PCDATA).getName() is null, if statement(null.
equals(name)) will throw null pointer exception.
