Folks,
I've found a serious regression in the TrueType handling in version
2.3.2. If you plan to use the native bytecode interpreter, I suggest
*not* to upgrade! Please wait for 2.3.3 which will be available soon,
I hope.
Werner
___
Freetype-
That is totally irrelevant to the bug at hand (well, probably not completely
;-)), but I cannot resist such an offer... Sorry to ALL the people out there
which already know that stuff.
James Cloos wrote:
> and probably is most often called by way of the macro:
>
> ,(freetype2/include/freetype/
On Mon, 2007-03-12 at 07:45 -0400, Werner LEMBERG wrote:
> Folks,
>
>
> I've found a serious regression in the TrueType handling in version
> 2.3.2. If you plan to use the native bytecode interpreter, I suggest
> *not* to upgrade! Please wait for 2.3.3 which will be available soon,
> I hope.
T
Hi folks,
I'm on it at the moment, but given that I'm dog sick at the moment with
39.5 ºC, it will probably take a few days
regards
- David
On Mon, 12 Mar 2007 13:37:43 -0400, "Behdad Esfahbod" <[EMAIL PROTECTED]> said:
> On Mon, 2007-03-12 at 07:45 -0400, Werner LEMBERG wrote:
> > Folks,
> >
Dear Sir,
It seems that quoting style `xxx' in C source comment
can make C compiler cause mismatching quoting error,
aslike:
[snip]
>checking CoreServices & ApplicationServices of Mac OS X... ok
>checking OS_INLINE macro is ANSI compatible... ./configure: command
>substitution: line 1: unexpecte
> It seems that quoting style `xxx' in C source comment can make C
> compiler cause mismatching quoting error, aslike:
Uh, oh! This is the first time I've heard this :-(
Please fix it in the CVS, and, if possible, send a bug report to the
compiler developers. It's probably a good idea to report
Dear Sir,
On Tue, 13 Mar 2007 07:59:43 +0100 (CET)
Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > It seems that quoting style `xxx' in C source comment can make C
> > compiler cause mismatching quoting error, aslike:
>
> Uh, oh! This is the first time I've heard this :-(
>
> Please fix it in th
> Sorry, the wrong was not C compiler.
OK.
> It seems that configure script tries to evaluate `OS_INLINE', then
> failed, and the generated conftest.c is interrupted and cannot be
> compiled. So, if forced to say, using backquote in the testing code
> for AC_TRY_COMPILE([], []), I ought have to
