|
Posted by Joost Diepenmaat on January 13, 2008, 7:42 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 magoo on January 13, 2008, 8:24 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 Joost Diepenmaat on January 13, 2008, 10:13 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 Ilya Zakharevich on January 13, 2008, 10:22 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 David Combs on February 11, 2008, 7:19 pm
Please log in for more thread options >[A complimentary Cc of this posting was NOT [per weedlist] sent to
>Ilya Zakharevich
>> > As I said: you are greatly mistaken about the intended semantic of int().
>> > You may want to read the documentation for clarification.
>
>> As I said, the existing state of documentation of Perl is, at most,
>> pitiful. (If you still do not realize this, I wrote some
>> [significant?] part of implementation of Perl's int(). *This* is why
>> I feel so hurt by this bug of mine. ;-)
>
>Thinking about it more, this illusion of grandeur may be a piece of my
>imagination ;-). I remember a lot of struggle to make int() and "%"
>conformant to `perldoc perlnumber'; I definitely implemented at least
>one of these - but I do not remember which.
>
>Sorry,
>Ilya
Am a bit confused about (1) the vocabulary being used
here and (2) about just what this bug you say you created is.
"Round down" (that was the term used earlier in the thread, yes?)
I always thought that had to do relative to a .5 or nearby. Clearly,
I'm wrong, but can someone explain it a bit more fully?
Int for positives meant truncation, I thought.
For negatives, hmmm, what you *want* for int(-3.999)?
Or would some people *reasonably* want one thing and others the other?
And now, for something completely different: Mod on negatives.
I think I recall that some languages and Knuth did it one way,
and other languages another.
And did different fields do it different ways?
(Sorry for asking such totally idiotically "basic" stuff! :-)
Thanks,
David
|
| Similar Threads | Posted | | measure time (hopefully in milliseconds) | October 25, 2004, 12:39 am |
| Current Time with 5 digits of milliseconds | May 12, 2008, 3:39 am |
| every(seconds => 4) | February 29, 2008, 1:30 pm |
| FAQ 4.15: How can I take a string and turn it into epoch seconds? | December 25, 2004, 12:03 pm |
| FAQ 4.15 How can I take a string and turn it into epoch seconds? | February 10, 2005, 6:03 am |
| FAQ 4.15 How can I take a string and turn it into epoch seconds? | April 25, 2005, 11:03 pm |
| FAQ 4.15 How can I take a string and turn it into epoch seconds? | July 11, 2005, 4:03 am |
| FAQ 4.15 How can I take a string and turn it into epoch seconds? | August 14, 2005, 10:03 am |
| How to run a perl script after an interval of 10 seconds | October 27, 2005, 7:09 am |
| FAQ 4.15 How can I take a string and turn it into epoch seconds? | December 4, 2005, 11:03 pm |
|
XML Sitemap