Wireshark-dev: [Wireshark-dev] size_t under Windows ...
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: Richard Sharpe <realrichardsharpe@xxxxxxxxx>
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
(何以解憂？唯有杜康。--曹操)