Wireshark mailing list archives
size_t under Windows ...
From: Richard Sharpe <realrichardsharpe () gmail com>
Date: Thu, 23 Nov 2017 14:12:51 -0800
Hi folks, especially Windows developers ... I am running into problems with this in my latest build: #if defined(_WIN32) char * cap_pipe_buf; /**< Pointer to the buffer we read into */ DWORD cap_pipe_bytes_to_read; /**< Used by pipe_dispatch */ DWORD cap_pipe_bytes_read; /**< Used by pipe_dispatch */ #else size_t cap_pipe_bytes_to_read; /**< Used by pipe_dispatch */ size_t cap_pipe_bytes_read; /**< Used by pipe_dispatch */ #endif I suspect that I should simply define both of those as size_t and get rid of the Windows specific stuff. Does any one else have an opinion? -- Regards, Richard Sharpe (何以解憂?唯有杜康。--曹操) ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- size_t under Windows ... Richard Sharpe (Nov 23)
- Re: size_t under Windows ... Helge Kruse (Nov 24)
- Re: size_t under Windows ... Dario Lombardo (Nov 24)
- Re: size_t under Windows ... Roland Knall (Nov 24)
- Re: size_t under Windows ... Graham Bloice (Nov 24)
- Re: size_t under Windows ... Dario Lombardo (Nov 24)
- Re: size_t under Windows ... Helge Kruse (Nov 24)
- Re: size_t under Windows ... Guy Harris (Nov 24)
- Re: size_t under Windows ... Richard Sharpe (Nov 24)
- Re: size_t under Windows ... Guy Harris (Nov 24)
- Re: size_t under Windows ... Richard Sharpe (Nov 24)