|
Posted by Mark Jason Dominus on July 9, 2005, 11:10 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 Sherm Pendley on July 9, 2005, 8:25 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 Mark Jason Dominus on July 10, 2005, 12:35 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 Kevin Michael Vail on July 10, 2005, 12:38 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 Threads | Posted | | Book: Higher-Order Perl: Transforming Programs with Programs | July 9, 2005, 5:11 pm |
| FAQ 3.5: How do I debug my Perl programs? | December 16, 2004, 12:03 am |
| FAQ 3.5: How do I debug my Perl programs? | December 17, 2004, 6:03 pm |
| FAQ 3.6 How do I profile my Perl programs? | January 26, 2005, 12:03 pm |
| FAQ 3.5 How do I debug my Perl programs? | February 25, 2005, 6:03 pm |
| FAQ 3.5 How do I debug my Perl programs? | April 8, 2005, 5:03 pm |
| FAQ 3.6 How do I profile my Perl programs? | April 24, 2005, 11:03 am |
| FAQ 3.5 How do I debug my Perl programs? | June 24, 2005, 11:03 am |
| FAQ 3.6 How do I profile my Perl programs? | July 10, 2005, 4:03 am |
| FAQ 3.5 How do I debug my Perl programs? | August 23, 2005, 4:03 am |
|
XML Sitemap