Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re: Subtracting Stringified Negative Numbers

by Moron (Curate)
on Jun 22, 2007 at 12:55 UTC ( #622781=note: print w/replies, xml ) Need Help??

in reply to Subtracting Stringified Negative Numbers

The '^' (carat) at the beginning causes the error. All else that follows never makes it to the parser.

^M Free your mind!

  • Comment on Re: Subtracting Stringified Negative Numbers

Replies are listed 'Best First'.
Re^2: Subtracting Stringified Negative Numbers (carrots)
by tye (Sage) on Jun 22, 2007 at 17:09 UTC

    Heh, you might want to read the thread (or even the entire original node) since there are no carets (nor even any carats, at least according to my scale) in these strings. Just FYI. :)

    - tye        

      Posts on this site occur in chronological order. The OP reveals that the error message blames '^\'. My mistake was simply that I didn't realise the parser intended this as a representation of ctrl-\ - a finding published later than my post. But obviously from your comment, you didn't know that either or didn't draw the correct inference.

      ^M Free your mind!

        Just to be clear, the root node showed output from Data::Dumper that could have clued you in that there were no carets in the strings. And at least two replies made this point very explicit quite a few hours before you posted despite your claim that it was "a finding published later than my post".

        Your mention of:

        Posts on this site occur in chronological order

        makes me suspect that you are referring to the order in which direct replies are sorted when displayed in a thread and that you made your conclusion based on the order displayed and that you didn't bother to glance at the timestamps (nor did you look carefully at the replies before originally replying).

        And your confusion on the timing makes me suspect that you were seeing direct replies sorted "newest first" (reverse chronological order). The site has long offered sorting of direct replies oldest first, newest first, or highest-reputation first but only recently was a bug fixed that meant "newest first" actually resulted in "oldest first" before that. So several people suddenly had their note order go from "oldest first" to "newest first" when that bug was fixed.

        Given the number of complaints, I began to suspect that perhaps the bug fix was actually impacting people who had not previously changed their User Settings to select "newest first" (and left it that way). Your reply was the straw that induced my camel to actually try to verify whether that was the case. I couldn't find evidence of that (Anonymous Monk sees nodes sorted chronologically and has no value defined for that setting and an old user that I'm pretty sure had not modified that setting had the default value and also sees nodes sorted chronologically) so I guess that fiddling and picking "newest first" (and leaving it) is just more common than I'd have expected (though there certainly could be more to it than that, just not something I was able to discover with my simple tests).

        Anyway, I hope that clarifies some things.

        - tye        

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://622781]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others imbibing at the Monastery: (4)
As of 2018-07-21 19:37 GMT
Find Nodes?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

    Results (450 votes). Check out past polls.