Re: [Jocr-devels] Fwd: compiling gocr 0.43 on MS Windows

[Peter M. <fee...@se...>]

Hi Joerg,

 > Can you tell me, why inline => __inline is necessary?

It is a Microsoft specific syntax, see

    http://msdn2.microsoft.com/en-us/library/z8y1yy88.aspx

"The inline keyword is available only in C++". I compile gocr
as non-C++. Otherwise both inline and __inline should work
(I didn't verify this). You may put in your ocr0.h

#ifdef WIN32
#define inline __inline
#endif

Also notice the inconsistency between pgm2asc.c and pgm2asc.h
in using "const" in pgm2asc.h

    wchar_t *wcschr (const wchar_t *wcs, wchar_t wc);

and not in pgm2asc.c

    wchar_t *wcschr (wchar_t *wcs, wchar_t wc)

Will you be adding deskewing in one of the next versions?

Peter Meijer


Seeing with Sound - The vOICe
http://www.seeingwithsound.com


Joerg Schulenburg wrote:
> Hi,
> 
> On Wed, 13 Dec 2006, Peter Meijer wrote:
> 
>> The Microsoft Windows executable for GOCR 0.43 is now also available,
>> ... while changing inline => __inline in ocr0.h, as with
>> previous releases.
> 
> Can you tell me, why inline => __inline is necessary?
> 
> It seems to me nonstandard to do so.
> Would a 
> 
> #ifndef __GNUC__
> static inline
> #endif
> int sq(...) {...}
> 
> help?
> 
> Joerg