Ticket #118 (enhancement)
Opened 2 years ago
Last modified 1 year ago
Recode audio.py in c++ for "all c++" usage.
Status: assigned
| Reported by: | eb | Assigned to: | jcorgan (accepted) |
|---|---|---|---|
| Priority: | normal | Milestone: | release-3.2 |
| Component: | no-python | Version: | 3.0svn |
| Keywords: | Cc: | ||
Explicit use of a particular audio source/sink makes the 'all c++' code brittle. audio.py should be recoded into C++ so that user prefererences are still followed when building 'all c++' versions of GNU Radio. See also ticket:116.
Change History
12/18/06 11:08:04: Modified by eb
- milestone changed from to-be-decided to release-3.1.
12/18/06 11:18:38: Modified by jcorgan
12/18/06 17:57:22: Modified by jcorgan
- status changed from new to assigned.
04/28/07 11:59:36: Modified by jcorgan
- milestone changed from release-3.1 to release-3.2.
One could debate that in the target usage model for C++ only apps (embedded systems), one already knows what one's audio hardware is, and would explicitly include the appropriate header file and link library. I'm not opposed to recoding audio.py in C++ but is it really needed?