Pop Quiz

VBScript Quiz Answers, Part Two

Fabulous Adventures In Coding — Sat, 26 Feb 2005 01:29:00 GMT

re: Pop Quiz

Eric Lippert — Thu, 29 Jul 2004 20:27:00 GMT

Indeed.

I'm not actually going to FIX it, mind you. I don't own that code anymore. Next time I see the owner, I'll mention it to him, but this is a pretty low-priority fix.

re: Pop Quiz

Steven Bone — Thu, 29 Jul 2004 20:24:00 GMT

Eric - talk about response times... 11:43 AM Nicholas Allen reports a possible bug. 12:01 PM Eric Lippert finds the internal source code, determines the problem, adds a warning in the code, and writes a response.

re: Pop Quiz

Eric Lippert — Thu, 29 Jul 2004 20:21:00 GMT

Right -- James has hit the nail on the head. There's only one place in the JScript code that converts strings to numbers, and that's the same code that is used in parseInt/parseFloat/etc, so that they remain consistent with each other. (Though there are in fact some oddities, which might be a good subject for a future entry.)

Your design is better -- the warning should have gone into the scanner, not into the portion of the parser which turns numeric literal tokens into expression nodes in the abstract syntax tree.

re: Pop Quiz

Nicholas Allen — Thu, 29 Jul 2004 19:49:00 GMT

Interesting. That is kind of weird to use a runtime function to do the conversion.

We check for bad octals in the scanner so the warning has already gone out before anyone gets their hands on the token.

re: Pop Quiz

James Mastros — Thu, 29 Jul 2004 19:19:00 GMT

For a while, perl had a bug whereby floating point numbers would be interpreted slightly differently depending on where they were used -- it hit very rarely, and only effected the last digit. The problem? Two different functions were being used, one for compile-time constants, one for arithemetic on strings holding floating-point numbers, that did the conversion ever-so-slightly differently. Perl has a much looser compiletime/runtime dichtomy then many languages, and will happily give you warnings at runtime when it feels the need, so that's not an issue there, but the lesson is still important -- stuble differences in behavior aren't generally a good thing, when your users expect two things to work the same way, and if you implement something twice, you'll end up with subtle differences in behavior.

re: Pop Quiz

Eric Lippert — Thu, 29 Jul 2004 19:01:00 GMT

Ah, how interesting. That's a bug.

I added the warning to the code path where an octal literal is evaluated as part of a numeric expression. Since as we've just seen, a label must not be an expression, the warning is never hit.

In this case we're not looking to evaluate an expression as a number. We need that thing as a canonical string. So we need to turn it into a number, and then turn it back into a string. For some odd reason, the routine that the compiler uses to do that is the same routine as is used at runtime by parseInt, rather than the routine used by the compiler in the main line expression evaluator. parseInt, being a runtime function, doesn't produce compile-time warnings.

I'm not sure why the compiler author made that choice -- I didn't write that part of the compiler.

re: Pop Quiz

Nicholas Allen — Thu, 29 Jul 2004 18:49:00 GMT

JScript .NET (jsc 7.10.3052 to be exact)

re: Pop Quiz

Eric Lippert — Thu, 29 Jul 2004 18:47:00 GMT

I don't get any error for either of those. Or are you talking about JScript .NET?

I talked a bit about malformed octal here:

http://blogs.msdn.com/ericlippert/archive/2003/10/23/53278.aspx

re: Pop Quiz

Nicholas Allen — Thu, 29 Jul 2004 18:43:00 GMT

Since we're talking about the quirks of numbers in object initializers...

Why doesn't

var x = { 08 : 0 };

whine about being a malformed octal literal?

var y = 08;

does.