-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use modern triple equals and change to js module #59
Open
Nikaoto
wants to merge
3
commits into
antimatter15:master
Choose a base branch
from
Nikaoto:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I happened to read through this and believe this change introduces a subtle bug. A few lines above in L334,
toFlatArray()
is called, but without a second argument, i.e.outBuffer
will beundefined
here. The expected behavior before was that in this case, a new array will be created, and indeedundefined == null
in JavaScript (the way it was before your change). Now the test is strict and fails therefore. As a consequence no array is created whenoutBuffer
isundefined
, which leads to an error. Maybe it would be best to just testif (!outBuffer) {
orif (outBuffer === undefined) {
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a correct remark. I should've noticed that when changing it.
In this case, however,
outBuffer
is never really undefined sincetoFlatArray
is only used once on L334 outside the function:And the variable
ebml
, defined on L297 can't become undefined since the only changes made to it are a few push methods. So, in this case, my changes don't introduce fatal bugs, but they're still dangerous considering future modifications made to the code might have an undefined array be passed totoFlatArray
.What's more, there's a better way to export whammy as a module for nodejs without having the browser give an annoying error for accessing a non-existent global
module.exports
.I'll fix both issues as soon as possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR actually fixes the second issue I wrote about: #46
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While it is true that the variable
embl
can't becomeundefiend
, it is actually the second parameter totoFloatArray()
(the parameteroutBuffer
) that I worry about. IftoFloatArray()
is called in L334 without this second argument, onlyembl
is passed in, which in turn is available as argumentarr
withintoFloatArray()
. The second parameter (outBuffer
) isundefined
in this situation and this results in an error if thearr
contents are non-objects and get pushed tooutBuffer
.The other changes look good to me though and the PR itself is certainly useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to have slipped my mind.
outBuffer
is definitely undefined when no second argument is passed totoFloatArray
.