add default message for pvget

[rerpha]

Adds a default message for pvget. I don't know if line 363 (the default case) was a bug as i could never get it to run. @ralphlange I found this after I showed you my (accidentally?) working PVAccess.

Maybe there's a good reason that pvget doesn't have this line but the other tools do, please let me know!

[AppVeyorBot]

✅ Build pvAccessCPP 1.0.100 completed (commit 6a0c4f85bf by @rerpha)

[AppVeyorBot]

✅ Build pvAccessCPP 1.0.101 completed (commit 84f932cae9 by @rerpha)

[AppVeyorBot]

✅ Build pvAccessCPP 1.0.102 completed (commit a9eb144842 by @rerpha)

[mdavidsaver]

I don't know if line 363 (the default case) was a bug as i could never get it to run.

That default case should be impossible so long as the switch is consistent with the string passed to getopt(). imo. any inconsistency should be an error. I usually combine default and '?' though.

Maybe there's a good reason that pvget doesn't have this line but the other tools do, please let me know!

I guess you are referring to caget?

It think it is a bit of a judgement call whether PVs is an error with pvget. With pvmonitor I think this should be.

Is it worth changing behavior at this point?

[rerpha]

Maybe there's a good reason that pvget doesn't have this line but the other tools do, please let me know!

I guess you are referring to caget?

It think it is a bit of a judgement call whether PVs is an error with pvget. With pvmonitor I think this should be.

Is it worth changing behavior at this point?

by other tools yes caget, but also pvput, pvinfo, pvmonitor all seem to give the "No pv name(s) specified. ('pvXXXX -h' for help.)" message - just thinking for consistency among the pv* utils it might be nice.

[AppVeyorBot]

✅ Build pvAccessCPP 1.0.111 completed (commit ef35bf3698 by @rerpha)

[anjohnson]

Please fix the indentation, these should line up with the fprintf() above.