Open
Conversation
Contributor
Can you clarify that is non-standard about it? |
Author
You can add -Wpedantic into Makefile. Result: |
Contributor
|
Ah, right. Does MSVC choke on it? On QuickJS-ng we somehow didn't run into this... |
Author
Maybe MSVC is use C89 default. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I found MSVC Compatibility #16
But it modified too many codes
And I tried MSVC 2022 to compile it today.
It just needs to be modified the JSValue casting because it's not standard C code.
If I want to build it with MSVC 2022,
I need to add -std:c11 -experimental:c11atomics option and metarutaiga@10f9f7c only.
Yeah, I dont like MSVC too.