Click here to get back home

FAQ 7.21 What's the difference between calling a function as &foo and foo()?
 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
FAQ 7.21 What's the difference between calling a function as &foo and foo()? PerlFAQ Server 11-15-2006
Get Chitika Premium
Posted by Dr.Ruud on November 15, 2006, 5:26 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 Tad McClellan on November 15, 2006, 7:55 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 Justin C on November 16, 2006, 7: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

Similar ThreadsPosted
FAQ 7.21: What's the difference between calling a function as &foo and foo()? December 2, 2004, 6:03 pm
FAQ 7.21 What's the difference between calling a function as &foo and foo()? March 14, 2005, 12:03 pm
FAQ 7.21 What's the difference between calling a function as &foo and foo()? June 10, 2005, 5:03 pm
FAQ 7.21 What's the difference between calling a function as &foo and foo()? September 16, 2005, 10:03 pm
FAQ 7.21 What's the difference between calling a function as &foo and foo()? September 3, 2006, 9:03 am
FAQ 7.21 What's the difference between calling a function as &foo and foo()? March 8, 2007, 9:03 am
FAQ 7.21 What's the difference between calling a function as &foo and foo()? August 10, 2007, 3:03 am
FAQ 7.22 What's the difference between calling a function as &foo and foo()? October 24, 2007, 9:03 am
FAQ 7.22 What's the difference between calling a function as &foo and foo()? January 9, 2008, 9:03 am
FAQ 7.21 What's the difference between calling a function as &foo and foo()? May 23, 2007, 3: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