If you read more carefully the code in DOMTreeErrorReporter.cpp you can
see that the implementation of the "error" and "fatalError" methods
first set the flag "I have seen an error" and then print on the console
the description of the error and its location. Nothing stops you from
storing those informations in a list that the main module can retrieve
and process, instead of simply retrieving the flag.
Alberto
harshabi wrote:
I saw the DOMPrint sample... The code doesnt tell where the error exists or
what the error is...
All that the DOMPrint does is that it checks whether errors exist or not and
if there are errors it
returns 4
if (!errorsOccured && !errReporter->getSawErrors())
{
//If there are no errors do some processing
}
else
retval = 4;
i wanted the else part to show me what the error is (for example error
exists in line no. 34 expected <suchandsuch> tag or something like that)...i
hope you understand.... Please help me....
Alberto Massari wrote:
Isn't the DOMTreeErrorReporter defined in the DOMPrint sample enough for
you to get started? What do you think is it missing?
Alberto
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
