OK, *that's* what Clang Cat was going on about:
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 15 Nov 2011 05:37:56 +0000 (05:37 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 15 Nov 2011 05:37:56 +0000 (05:37 +0000)
commit5fd69cb419d94d9a87b9f7c63305f79365f54499
treea1ed7e0cbdb78e8d4c8328a99b8fa85f493b065e
parent95fe2da38a0092fc7b0e2bc85b9b364980e6b1c3
OK, *that's* what Clang Cat was going on about:

packet-dcerpc-pn-io.c:8438:17: warning: Although the value
stored to 'prm_flag2' is used in the enclosing expression, the
value is never actually read from 'prm_flag2'

OK, thanks for telling me that, technically,

prm_flag1 = prm_flag2 = 0;

can be implemented by storing the 0 into prm_flag1 directly rather than
storing 0 into prm_flag2 and copying it to prm_flag1.  Yes, you can haz
cheeseburger.

I guess it would matter if we were actually depending on some
side-effect of fetching prm_flag2, but we're not.  Rewrite this one to
squelch the complaint.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@39841 f5534014-38df-0310-8fa8-9805f1628bb7
plugins/profinet/packet-dcerpc-pn-io.c