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 |
|
|
||
| FORCE_INLINE Formatter& format(format_t f) { xfmt = f; return *this; } | ||
|
|
||
| FORCE_INLINE Formatter& asString(bool b) { xstring = b; return *this; } |
There was a problem hiding this comment.
asString() seems too generic for this quite specific "treat byte array as string" modifier.
This emulates the behavior of the caget -S option. Byte arrays are displayed as strings.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| 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) |
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