in reply to bug in Perl compilation?

To build on ikegami's reply, this is a faq. Check perldoc -q 'long decimals'.

Said this, I recommend using <code> tags for your code. Also, as $Larry said, the shebang line is much like a "hello" and the __END__ token is much like a "bye", so they should be more than enough to visually mark the beginning and the end of your code.

Replies are listed 'Best First'.
Re^2: bug in Perl compilation?
by bkgallo (Initiate) on Dec 22, 2005 at 16:33 UTC
    Thanks everyone for your help. I think I'll use the method mentioned in "perldoc -q 'long decimals'" to resolve this.

    But from an algorithmic perspective, it still irks me that these two numbers, which represent the exact same value, get converted to two slightly different binary values on this Linux system. I for one would call that a bug in the C compiler.

      Well, I don't have the slightest idea if it is actually a bug and if it is a bug of the C compiler or who knows what, but salva says it should not, and I don't know whether to trust him, but definitely he seems to be knowledgeable, certainly (much much) more than I am, so I'd take his word for the moment...