includes: avoid confusing the preproccesor

[Austin English]

See http://savannah.nongnu.org/bugs/?38557

====

In fact, after some investigation, I found out that it's the correct
behavior as '0xfe+1' is considered as a number token by the preprocessor.
I've learned something today :)

>From the C89 standard:
" 3.1.8 Preprocessing numbers:
A preprocessing number begins with a digit optionally preceded by a period
(.) and may be followed by letters, underscores, digits, periods, and e+,
e-, E+, or E- character sequences."

There is a similar rule in C99 (see 6.4.8).

The solution is to put a space before the sign.
====

-- 
-Austin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20130329/2c563d17/attachment.html>
-------------- next part --------------
diff --git a/include/nb30.h b/include/nb30.h
index 0a2336e..303e78b 100644
--- a/include/nb30.h
+++ b/include/nb30.h
@@ -128,7 +128,7 @@ typedef struct _NAME_BUFFER
 typedef struct _LANA_ENUM
 {
 	UCHAR length;
-	UCHAR lana[MAX_LANA+1];
+	UCHAR lana[MAX_LANA + 1];
 } LANA_ENUM, *PLANA_ENUM;
 
 typedef struct _FIND_NAME_HEADER