parseInt mystery about art-of-node HOT 2 CLOSED

why does typeof(fileContents); return object instead of string

If no encoding is specified for readFile, then the raw buffer is returned which is why typeof is reporting an object. The Buffer class provides a method to inspect an object to see if it is a buffer (isBuffer).

Buffer.isBuffer(fileContents) // should return true

To make fileContents a string, you can either provide an encoding option for readFile or call toString on fileContents.

why will this example work without parseInt?

parseInt converts its string param to a string if it isn't one already (effectively fileContents.toString()). Increment (++) doesn't document as such, but with a little testing I saw it behave the same as you could expect a string when performing arithmetic.

var assert = require('assert');

function increment(n) {
  nn = n++
  // increment returns s as a number to nn
  assert.equal(typeof(nn), 'number')
  // n is now also a number (not original type) and has value incremented
  assert.equal(typeof(n), 'number')
  assert.equal(n, 2)
}

// strings as numbers
s = '1'
assert.equal(typeof(s), 'string')
increment(s)


// buffers as numbers
b = new Buffer('1')
assert(Buffer.isBuffer(b))
increment(b)

Mystery solved?

from art-of-node.

Awesome @maxbeatty!! It's a mystery no more.

You also gave me some neat tests to play with as well! Thanks for that. A great experiment for the making of new spells and potions.

Cheers!

from art-of-node.