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
schelp Object.dump
update: more explanation with case examples
#6292
Open
prko
wants to merge
19
commits into
supercollider:develop
Choose a base branch
from
prko:topic/SChelp-dump-more-explanation
base: develop
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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
schelp Object.dump
update: more explanation with case examples
#6292
prko
wants to merge
19
commits into
supercollider:develop
from
prko:topic/SChelp-dump-more-explanation
Conversation
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
added more explanation on equality, identity and dump
Help document update: equality, identity and dump across four files
This reverts commit 64de778.
update documentation: equlity, identity and dump across files uploaded
…-_equality_identity_dump
added more explanation on equality, identity and dump
Help document update: equality, identity and dump across four files
This reverts commit 64de778.
update documentation: equlity, identity and dump across files uploaded
…om/prko/supercollider into topic/SChelp-dump-more-explanation
prko
changed the title
schelp update: .dump more explanation with examples by cases
schelp May 5, 2024
Object.dump
update: more explanation with case examples
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.
Purpose and Motivation
The explanation of .dump is too minimal and abstract. I have summarised what I learned from scsynth.org and the old mailing list.
In particular, the following thread was helpful:
https://scsynth.org/t/understanding-the-result-of-dump-low-level-data-for-float-hexadecimal-for-string-gc-fmt-flg-and-set/8553/3
https://listarc.cal.bham.ac.uk/lists/sc-users-2016/msg50531.html
Thanks to @telephon, @dkmayer, @adcxyz, @jamshark70, and @mossheim!
I have added explanations that are as detailed as possible and as simple as possible for those new to SuperCollider with no programming experience.
I hope this can be approved and merged if the content is correct.
In the hope that someone will let me correct the wrong information rather than be ignored, so that this PR can help someone like me without having to search the internet.
PDF files of the corresponding parts in the object help file:
Types of changes
To-do list