Add -S option to pvget/pvmonitor to stringify byte arrays - #105
Conversation
|
❌ Build pvDataCPP 1.0.72 failed (commit ec43e93fce by @JJL772) |
|
❌ Build pvDataCPP 1.0.72 failed (commit ec43e93fce by @JJL772) |
|
❌ Build pvDataCPP 1.0.72 failed (commit ec43e93fce by @JJL772) |
|
❌ Build pvDataCPP 1.0.72 failed (commit ec43e93fce by @JJL772) |
|
Appveyor builds with older VMs need a newer version of pip. Nothing to do with this PR, I think we need to fix the CI in Base. |
|
Nothing to do with this PR - agreed. The CI builds of Base don't have this issue - it's the CI configuration of this module that needs fixing. |
|
Just realized I forgot to open the corresponding PR in pvAccess to actually add the |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 4 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
❌ Build pvDataCPP 1.0.75 failed (commit f0ac7e2c61 by @JJL772) |
|
✅ Build pvDataCPP 1.0.75 completed (commit f0ac7e2c61 by @JJL772) |
c49b615 to
47bd85f
Compare
|
✅ Build pvDataCPP 1.0.77 completed (commit 8c0f4011a6 by @JJL772) |
8038a79 to
7a4823d
Compare
|
✅ Build pvDataCPP 1.0.78 completed (commit 9491dc27ab by @JJL772) |
|
✅ Build pvDataCPP 1.0.79 completed (commit 6eb459f812 by @JJL772) |
|
✅ Build pvDataCPP 1.0.80 completed (commit 5097577f2b by @JJL772) |
Behaves similar to caget's '-S' option, except that NULL termination is not respected. Instead, string length is determined solely based on the array length, with single trailing NULLs being stripped. All other characters within the range [0, len) are escaped and/or printed.
d5e09b2 to
f2f5d65
Compare
|
❌ Build pvDataCPP 1.0.96 failed (commit 630cb7f8c6 by @JJL772) |
5 participants
This emulates the behavior of the caget -S option. Byte arrays are displayed as strings.
Example (without -S):
Example (with -S):
pvAccess PR: epics-base/pvAccessCPP#222