Click here to get back home

Regex won't work
 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
Regex won't work =?ISO-8859-1?Q?Christian_Watte 02-09-2006
|--> Re: Regex won't work =?ISO-8859-1?Q?...02-09-2006
`--> Re: Regex won't work Gunnar Hjalmars...02-09-2006
Get Chitika Premium
Posted by =?ISO-8859-1?Q?Christian_Watte on February 9, 2006, 5:14 pm
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 =?ISO-8859-1?Q?Christian_Watte on February 9, 2006, 5:15 pm
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 Gunnar Hjalmarsson on February 9, 2006, 7:12 pm
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
Hrs of work on regex: please help July 26, 2004, 6:51 pm
Can someone 'splain why this regex won't work both ways? April 14, 2008, 1:08 pm
Regex: Backreferences do not work inside quantifiers? March 7, 2006, 1:56 pm
regex bug (comments within regex not as robust) October 27, 2005, 12:01 pm
FAQ 4.6 Why doesn't & work the way I want it to? May 13, 2005, 5:03 am
FAQ 4.6: Why doesn't & work the way I want it to? November 7, 2004, 6:03 am
FAQ 4.6: Why doesn't & work the way I want it to? December 2, 2004, 12:03 pm
Why does this work? December 20, 2004, 5:57 pm
Why doesn't this work? January 18, 2005, 3:33 pm
FAQ 4.6 Why doesn't & work the way I want it to? February 12, 2005, 12:03 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap