mscdex
mscdex
Would it be possible to land this soon? For what it's worth I've gone ahead and applied the changes (fixing several merge conflicts) on top of v0.8.0 and I have...
What warning messages are you referring to? Can you give examples?
Looks like this was fixed in 2.17.0.
@gazebosx3 As @charmander said, that's not possible. You will need to count the bytes yourself as the file streams in if you need the total size when the stream ends.
I've fixed the build errors in my fork here: https://github.com/mscdex/node-compress However, there seems to be some issues with the addon itself which I have not figured out yet.
Yes, what @BurningEnlightenment said. The example of simply casting to a char array won't work because of the leading zero bytes causing early termination. Now that I've thought about it...
Oops, guess I shouldn't think before coffee.... the non-plain codec changes won't be that trivial. I really only need 16-bit decoding, so that makes it a little easier. I'm still...
Thanks, that got me started in the right direction. FWIW the byte mask pattern ended up needing to be (at least for little endian?): ``` -1, -1, -1, -1, -1,...
The main purpose is to skip whitespace, but all other invalid characters should be ignored as well. The reason being I need it for backwards compatibility with an existing base64...
I had a gut feeling that having a separate `decode16` would be faster, but I never got around to verifying that. Some questions: 1. @mayeut I've started looking at your...