Content-Length: 192335 | pFad | http://github.com/vitreo12/omni/issues/140

9E buffers: should Omni_UGenSetBuffer accept a "void* value" instead of "const char* value"? · Issue #140 · vitreo12/omni · GitHub
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.

Sign up for GitHub

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

Jump to bottom

buffers: should Omni_UGenSetBuffer accept a "void* value" instead of "const char* value"? #140

Open
vitreo12 opened this issue Feb 10, 2021 · 0 comments
Open

buffers: should Omni_UGenSetBuffer accept a "void* value" instead of "const char* value"? #140

vitreo12 opened this issue Feb 10, 2021 · 0 comments

Comments

@vitreo12
Copy link
Owner

No description provided.

@vitreo12 vitreo12 changed the title buffers: should Omni_UGenSetBuffer accept a void* as value? buffers: should Omni_UGenSetBuffer accept a "void* value" instead of "const char* value"? Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vitreo12








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://github.com/vitreo12/omni/issues/140

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy