On Oct 1, 2015, at 9:53 AM, Alexis La Goutte wrote:
> Yes, there is a "warning" with GCC from some month...
>
> ../../epan/proto.h:2740:54: warning: anonymous variadic macros were
> introduced in C99 [-Wvariadic-macros]
Perhaps we need to turn on the "use C99" flag for some compilers, includi
Yes, there is a "warning" with GCC from some month...
../../epan/proto.h:2740:54: warning: anonymous variadic macros were
introduced in C99 [-Wvariadic-macros]
Not problem for me, to allow variadic macro !
Regards,
On Thu, Oct 1, 2015 at 6:31 PM, Graham Bloice
wrote:
>
> On 1 October 2015 a
On 1 October 2015 at 17:25, Peter Wu wrote:
> #include
> #define FOO(fmt, ...) printf(fmt, #__VA_ARGS__, __VA_ARGS__)
> int main() {
> return FOO("%s test %d\n", 1);
> }
>
VS2013 appears to be happy, compiling the file with a .c extension:
c:\temp>cl var.c
Microsoft (R) C/C++
Hi,
Use of variadic macros has been discussed in the past
(https://www.wireshark.org/lists/wireshark-dev/201209/msg00142.html),
but at that time it was dropped because it was deemed not supported well
enough across compilers.
Now apparently commit v1.11.3-rc1-2203-geee21a6 added
proto_tree_add_fl
> On Oct 1, 2015, at 08:35, mman...@netscape.net wrote:
>
> But doesn't any of these potential representations (mostly network prefix)
> require a specific field type (and not a display type) for display filtering
> purposes?
>
I don't think so. You can use an FT_UINT32 and just tweak the df
But doesn't any of these potential representations (mostly network prefix)
require a specific field type (and not a display type) for display filtering
purposes?
-Original Message-
From: Jeffrey Smith
To: Developer support list for Wireshark
Sent: Thu, Oct 1, 2015 1:46 am
Subject:
Hi all,
in my company we just received the following email from Symantec indicating
that the EV signing will soon be mandatory:
"On October 27, 2015, all new Kernel and User Mode driver submissions will
need to be made via the Windows Hardware Developer Center Dashboard portal
and signed by an Ex
> On 30 Sep 2015, at 02:34, Gerald Combs wrote:
>
> Unless anyone has any objections I'd like to create the Wireshark
> master-2.0 branch this upcoming Monday, October 5 followed by the 2.0rc1
> release in mid to late October.
>
> The big, obvious change for 2.0 will be the new UI. As the page
