Skip to content
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

scsynth: implement /version command #2546

Merged
merged 5 commits into from Dec 11, 2016

Conversation

nhthn
Copy link
Contributor

@nhthn nhthn commented Dec 9, 2016

This fixes #2544 for scsynth, but not for supernova.

@vivid-synth
Copy link
Member

I'm not aware of how to contribute to someone else's pull request, but I'd be happy to work on the supernova equivalent. I think we shouldn't add features to one synth without supporting them on the other.

packet.addi(SC_VersionMinor);
packet.addtag('s');
packet.adds(SC_VersionPatch);

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd love to add SC_CommitHash too!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. What about SC_Branch?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SC_CommitHash is enough to tell us exactly what code we're running (unless the user made mods of course 😄 ). Then again, if this would be useful to someone there's no real reason not to add it

@vivid-synth
Copy link
Member

vivid-synth commented Dec 11, 2016

@snappizz did you want to add SC_Branch? Else, any objections, or are we good to merge? (I should add, looks good to me)

@Sciss
Copy link
Contributor

Sciss commented Dec 11, 2016

May I suggest that this be symmetric with scsynth -v? Currently it prints scsynth 3.7.2 for releases, and I think scsynth 3.7.2 (xyz) with build number for non-releases (?). So can we make sure that [/version_reply, name, maj, min, patch, commit-hash] will be identical to name maj.min.patch (commit-hash) when using the shell switch?

@nhthn
Copy link
Contributor Author

nhthn commented Dec 11, 2016

@Sciss yes, they both get their info from the same header file, SC_Version.hpp.

@vivid-synth vivid-synth merged commit a909bf1 into supercollider:master Dec 11, 2016
@vivid-synth
Copy link
Member

Nice!

@samaaron
Copy link

Ace - thanks so much :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants