Handle unprintable objects better in print()#834
Merged
bnoordhuis merged 2 commits intoquickjs-ng:masterfrom Jan 18, 2025
Merged
Handle unprintable objects better in print()#834bnoordhuis merged 2 commits intoquickjs-ng:masterfrom
bnoordhuis merged 2 commits intoquickjs-ng:masterfrom
Conversation
Before this commit, such objects were printed as `<exception>` because print() and console.log() had no good way to turn them into strings. Instead perform the C equivalent of Object.prototype.toString.call(o) and print the result (which can still error but at least we tried.) Fixes: quickjs-ng#832
saghul
approved these changes
Jan 18, 2025
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
2 participants
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.
Before this commit, such objects were printed as
<exception>because print() and console.log() had no good way to turn them into strings.Instead perform the C equivalent of Object.prototype.toString.call(o) and print the result (which can still error but at least we tried.)
Fixes: #832