Click here to get back home

Did not find leading dereferencer, detected at offset
 Home | NewsGroups | Search | About
Login Password
Register Now! Lost Password?
 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
Did not find leading dereferencer, detected at offset sfelkes 09-16-2006
Get Chitika Premium
Posted by sfelkes on September 16, 2006, 5:19 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 Christian Winter on September 16, 2006, 7:03 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 Ben Morrow on September 16, 2006, 7:39 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
Did not find leading dereferencer, detected at offset September 16, 2006, 5:20 am
Did not find leading dereferencer September 6, 2006, 10:38 am
"Did not find leading dereferencer" - new findings to an old puzzle October 23, 2006, 8:08 am
unpack with offset (skip, X) won't work October 7, 2006, 12:51 pm
12 hour clock and offset problem June 16, 2007, 11:40 am
Scan forward n lines from specified file offset November 5, 2006, 2:33 pm
time zone offset calc with localtime and gmtime April 4, 2005, 6:07 pm
update: timezone offset calc and date formatting April 8, 2005, 1:32 pm
Need help to ignore leading spaces April 4, 2006, 11:54 am
Leading Space with REGEX March 29, 2007, 12:20 pm

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML SitemapXML Sitemap