SIG

Home | NewsGroups | Search | About

comp.lang.perl.misc

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

SIG

Petr Vileta

10-03-2007

Re: SIG

Ben Morrow

10-04-2007

Re: SIG

Petr Vileta

10-04-2007

Re: SIG

Paul Lalli

10-04-2007

Re: SIG

Ben Morrow

10-04-2007

Re: SIG

Big and Blue

10-04-2007

Re: SIG

Petr Vileta

10-05-2007

Re: SIG

Big and Blue

10-05-2007

Posted by Petr Vileta on October 3, 2007, 9:41 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 Ben Morrow on October 4, 2007, 7:57 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 Petr Vileta on October 4, 2007, 11:07 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 Paul Lalli on October 4, 2007, 11:30 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 October 4, 2007, 12:11 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

Our other projects:

Art Dolls, Fairies and Mermaids - Sunnyfaces.net

Roy's Linux, Programming and Search Engines messages

1-Script XML Sitemap

XML Sitemap