Click here to get back home

problem with XML::Parser dying on errors...
 Home | NewsGroups | Search | About
Login Password
Register Now!
 comp.lang.perl.misc    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content
Subject Author Date
problem with XML::Parser dying on errors... Bruno Boettcher 02-07-2006
Get Chitika Premium
Posted by Bruno Boettcher on February 7, 2006, 4:48 am
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Posted by xhoster on February 7, 2006, 10:34 am
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Posted by Tad McClellan on February 8, 2006, 1:25 am
Please log in for more thread options
>>
>> [snip]
>>
>> > if I print "$1\n",
>> > the file prints just fine. But, if I do something like print "$1 after
>> > \n", the whole output is messed up. If I print "before $1\n", nothing
>> > prints at all. If I print "before $1 after\n", only after prints.
>>
>> not really sure, but could be a rogue "\r" in $1,


> There
> is a rogue carriage return (0xd) in the string

> Is there something I can do to deal with this
> situation?


Repair the corrupted file:

perl -p -i -e 'tr/\r//d' bad_file


--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas

Similar ThreadsPosted
Logging Errors (Instead of Just Dying) November 26, 2005, 4:35 pm
ld synbol errors building XML::Parser on AIX 5.2 June 30, 2005, 2:10 pm
little problem with xml::dom::parser January 22, 2008, 9:39 am
Hi Experts Please help :: Problem in Bio-Parser....with XML-RPC call July 30, 2006, 6:47 am
Problem with body text extraction with HTML::Parser December 13, 2005, 3:29 pm
XML-Parser to XML-Parser communication (encoding issues?) September 13, 2005, 2:53 pm
Script dying at opendir() April 27, 2005, 9:48 am
Re: comp.lang.* newsgroups seems dying November 24, 2008, 11:04 am
Re: comp.lang.* newsgroups seems dying November 26, 2008, 8:36 am
Re: comp.lang.* newsgroups seems dying November 26, 2008, 8:44 am

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap