Re: [Wireshark-dev] const'ness of value_string_ext

2014-07-25 Thread darkjames-ws
Hi, On Thu, Jul 24, 2014 at 04:35:07PM -0400, Kevin Cox wrote: 2: Change everything. Pros: - Full compiler error checking and type safety. Cons: - Hard - May change dissector API. I was wondering what everyone else thought and what should be done to improve the safety of this code. a/

Re: [Wireshark-dev] Change in wireshark[master]: Skip the NCP dissector when building on Windows without Python

2014-07-25 Thread Joerg Mayer
Does it really make sense to allow Windows builds without python installed? IMO we should by now require python to be present to be able to build on Windows (or any other plattform). Ciao Jörg PS: In my opinion this is one of the cases which need to be discussed on this list - too many

Re: [Wireshark-dev] const'ness of value_string_ext

2014-07-25 Thread Kevin Cox
On 25/07/14 03:01, darkjames...@darkjames.pl wrote: Hi, On Thu, Jul 24, 2014 at 04:35:07PM -0400, Kevin Cox wrote: 2: Change everything. Pros: - Full compiler error checking and type safety. Cons: - Hard - May change dissector API. I was wondering what everyone else thought and what

Re: [Wireshark-dev] Change in wireshark[master]: Skip the NCP dissector when building on Windows without Python

2014-07-25 Thread Bill Meier
On 7/25/2014 8:52 AM, Joerg Mayer wrote: Does it really make sense to allow Windows builds without python installed? IMO we should by now require python to be present to be able to build on Windows (or any other plattform). +1 Ciao Jörg PS: In my opinion this is one of the cases

Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available

2014-07-25 Thread Jeff Morriss
On 07/22/14 16:27, Wireshark announcements wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.0rc3. This is a public release candidate for Wireshark 1.12.0. Hmm, the source tarball isn't in the expected directory (rc2 is still there):