From 34766a1928881f8a9a609b432fd6c4cbc7a0ee7a Mon Sep 17 00:00:00 2001 From: "Dimitrie O. Paun" Date: Tue, 13 May 2003 04:48:11 +0000 Subject: [PATCH] Fix a few style issues. --- documentation/winelib-intro.sgml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/winelib-intro.sgml b/documentation/winelib-intro.sgml index 1873fceafce..657c5389b0d 100644 --- a/documentation/winelib-intro.sgml +++ b/documentation/winelib-intro.sgml @@ -50,13 +50,13 @@ Winelib. But the converse is not true. You can also build Winelib and Winelib applications on platforms not supported by Wine, typically platforms with a non i386 processor. But this is still - pretty much an uncharted territory. It would be more reasonable to - first target one of the more mundane i386-based platforms first. + pretty much uncharted territory. It would be more reasonable to + target one of the more mundane i386-based platforms first. The main difference is that the compiler becomes much more important. - It is highly recommended that you use gcc, g++, - and the GNU binutils. The more recent your gcc compiler the better. + It is highly recommended that you use gcc, g++, and the GNU binutils. + The more recent your gcc compiler the better. For any serious amount of code you should not consider anything older than gcc 2.95.2. The latest gcc snapshots contain some useful bug fixes and much better support for anonymous structs and unions. This