Under $firefox/obj-x86_64-unknown-linux-gnu/dist/bin, there is a test
module called "TestParser". I was wondering that should be the input
file to this module? I tried pure html file of a page, but got the
error information "Unable to create a sink".
> Under $firefox/obj-x86_64-unknown-linux-gnu/dist/bin, there is a test
> module called "TestParser". I was wondering that should be the input
> file to this module? I tried pure html file of a page, but got the
> error information "Unable to create a sink".
It's not used any more though, it only tests the old parser that
lives under parser/htmlparser/ -- the HTML5 parser that we use
now lives under parser/html
Thanks. But is there a separate test module for the new parser, just
like TestParser for the old parser? If not, is there a way to study
the performance of the parser only?
Thanks,
Yuhao
On Jan 2, 6:49 am, Mats Palmgren <mats...@gmail.com> wrote:
> > Under $firefox/obj-x86_64-unknown-linux-gnu/dist/bin, there is a test
> > module called "TestParser". I was wondering that should be the input
> > file to this module? I tried pure html file of a page, but got the
> > error information "Unable to create a sink".
> It's not used any more though, it only tests the old parser that
> lives under parser/htmlparser/ -- the HTML5 parser that we use
> now lives under parser/html
> Thanks. But is there a separate test module for the new parser, just
> like TestParser for the old parser? If not, is there a way to study
> the performance of the parser only?
I don't know. Henri might know how to test performance of the new
HTML parser.
> On Jan 2, 6:49 am, Mats Palmgren<mats...@gmail.com> wrote:
>> On 12/31/2011 10:37 PM, Yuhao wrote:
>>> Hi All,
>>> Under $firefox/obj-x86_64-unknown-linux-gnu/dist/bin, there is a test
>>> module called "TestParser". I was wondering that should be the input
>>> file to this module? I tried pure html file of a page, but got the
>>> error information "Unable to create a sink".
>> It's not used any more though, it only tests the old parser that
>> lives under parser/htmlparser/ -- the HTML5 parser that we use
>> now lives under parser/html
