[prev in list] [next in list] [prev in thread] [next in thread]
List: wine-devel
Subject: Re: itss: Use BOOL type where appropriate
From: Nikolay Sivov <bunglehead () gmail ! com>
Date: 2014-02-28 16:24:37
Message-ID: 5310B845.1040305 () gmail ! com
[Download RAW message or body]
On 2/28/2014 20:17, Fr=E9d=E9ric Delanoy wrote:
> ---
> dlls/itss/lzx.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/dlls/itss/lzx.c b/dlls/itss/lzx.c
> index 01a9492..9e343da 100644
> --- a/dlls/itss/lzx.c
> +++ b/dlls/itss/lzx.c
> @@ -85,14 +85,14 @@ struct LZXstate
> ULONG window_posn; /* current offset within the window */
> ULONG R0, R1, R2; /* for the LRU offset system */
> UWORD main_elements; /* number of main tree elements */
> - int header_read; /* have we started decoding at all yet? */
> + BOOL header_read; /* have we started decoding at all yet? */
> UWORD block_type; /* type of this block */
> ULONG block_length; /* uncompressed length of this block */
> ULONG block_remaining; /* uncompressed bytes still left to decode */
> ULONG frames_read; /* the number of CFDATA blocks processed */
> LONG intel_filesize; /* magic header value used for transform */
> LONG intel_curpos; /* current offset in transform space */
> - int intel_started; /* have we seen any translatable data yet? */
> + BOOL intel_started; /* have we seen any translatable data yet? */
>
This is a part of another project, I don't think we need it to differ =
more than it does already.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic