[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[scew-users] RE: Regarding issue when using Stream parser
From: |
Anup Rao |
Subject: |
[scew-users] RE: Regarding issue when using Stream parser |
Date: |
Mon, 13 Sep 2010 23:43:05 -0700 |
Hi Aleix,
I tested the code after applying the fix. I can confirm that the behavior is
now as expected.
Additionally I noticed that, for the SCEW library to compile on ARM platform,
we need to replace SCEW_EOF with (XML_Char)SCEW_EOF in writer_file.c at lines
133 and 136. (I am currently using SCEW version 1.1.1).
Regards,
Anup
-----Original Message-----
From: Aleix Conchillo Flaqué [mailto:address@hidden On Behalf Of Aleix
Conchillo Flaqué
Sent: Tuesday, September 14, 2010 4:17 AM
To: Anup Rao
Cc: address@hidden
Subject: Re: Regarding issue when using Stream parser
On 09/13/2010 04:48 PM, Anup Rao wrote:
> Hi Alex,
>
Hello Anup (btw, my name is Aleix, not Alex).
> Following some of the changes suggested in the previous mail, I was able to
> parse data as required. However, I have come across a strange problem when
> using the stream parser. In relation to the split chunks that I was trying to
> handle, I have observed a difference in behavior.
>
> If Portion A is '<chunk><n v="0"/><n ' and, portion B is 'v="0"/></chunk>',
> then the stream parsing succeeds.
>
> If Portion A is '<chunk><n v="0"/><n' and, portion B is ' v="0"/></chunk>',
> then the stream parsing fails reporting expat error (Invalid token).
>
> The position of the SPACE character seems to affect the behavior. I have
> attached a simple example to demonstrate the issue. The issue is reported as
> an expat error, I hope you can throw some light on the matter. Kindly let me
> know your thoughts on the issue.
>
You are right, I have tried it and this is actual a real bug. I have
already fixed it. By now, you can comment the line 346 to 350 in parser.c.
Let me know if it works.
Best regards,
Aleix
CONFIDENTIAL COMMUNICATION -- The information in this e-mail (including any
attachments) is confidential and proprietary to PRYSM, INC. and intended only
for the sole use of the intended recipient. If you have received this
communication in error, then any review, dissemination, distribution, or
copying of this message is strictly prohibited, and please permanently delete
this message (including any copies of this e-mail and any attachments thereto)
and notify us immediately by return e-mail or by forwarding this email to Susan
Kent at address@hidden