Int32Array bug for some (sometimes older) browser

[dominictarr]

Int32Array bug for some (sometimes older) browser

[djcoin]

By the way,
I got a "Uncaught Error: Unexpected "\u0000" at position 0 in state START " when commenting out the "if(process.browser)" part and using new Buffer (with the browserify-buffer shim) :s

[mattsgarlata]

Here is a fix that worked for us: SpiderStrategies@2544fd0

[dominictarr]

oh sorry I missed this issue the first time - this shouldn't really be a problem now days because of https://github.com/feross/buffer <- complete polyfil for buffer in all browsers.
You should get this if you use a recent browserify

[dominictarr]

@mattsgarlata does you code still work if you use Int8Array ? I it looks like you are allocating 4 bytes per input byte. Also, you could just create a Int8Array with the necessary length and then set it's values instead of creating an array and then turning it into an typed array

[nathanbowser]

@dominictarr We're just relying on using the buffer polyfill in the browser, now that it's supported. I don't think there's a reason to have the if (process.browser) check anymore, right?

[dominictarr]

that is correct, we could remove it.

[mattsgarlata]

I think it would be a good idea to remove it, since it doesn't work with unicode.

[dominictarr]

okay, it's removed in 0.8.3