Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Mon, 07 May 2018 07:33:16 +0200 (CEST), Werner LEMBERG wrote: > You would only check the return value of `FT_Done_Face' if your code > gets an `FT_Face' handle that it doesn't manage by itself (rather > unlikely, but who knows). In this situation it could happen that the > handle is NULL, and

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Mon, 7 May 2018 14:34:26 +0900, suzuki toshiya wrote: > Thus, making FreeType abort immediately by a bad > font, it can make some environment quite inconvenient. I’m not sure where you get such an idea from... ___ Freetype mailing list

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread suzuki toshiya
I guess, if the original request were something like: "there are so many existing applications which ignore the errors from FT_Done_Face or FT_Done_Library. I know no concrete examples of these errors, I want to collect the information on these errors, so I want to have some hook into these

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Werner LEMBERG
>> You only get an error code if `FT_Done_Face' is called with an >> invalid handle, something which doesn't happen in a normal FreeType >> workflow. > > What are you supposed to do when it does happen? You would only check the return value of `FT_Done_Face' if your code gets an `FT_Face'

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Sun, 6 May 2018 23:33:16 +0200, Gregor Mückl wrote: > On 5/6/2018 10:54 PM, Lawrence D'Oliveiro wrote: > >> In the process of recovering from the error in disposing of the >> first one, do you try to dispose of the second one? > > This could potentially happen ... I know it can

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Mon, 07 May 2018 06:55:27 +0200 (CEST), Werner LEMBERG wrote: > You only get an error code if `FT_Done_Face' is called with an > invalid handle, something which doesn't happen in a normal FreeType > workflow. What are you supposed to do when it does happen?

Re: [ft] FreeType 2.9 for iOS

2018-05-06 Thread R0b0t1
Post exact errors and download homebrew (https://brew.sh). You will need Xcode. Check the following: https://github.com/jkyin/Compile-Freetype-For-iOS https://github.com/cdave1/freetype2-ios Or: cmake -D IOS_PLATFORM=OS -G Xcode Cheers, R0b0t1 On Sun, May 6, 2018 at 9:12 PM, 刘小龙

[ft] FreeType 2.9 for iOS

2018-05-06 Thread ??????
Hello: I would like to ask, how to compile freetype 2.9 for iOS, I run on the Mac. /configure There is an error in the lack of zlib, bzip2, libpng library, how to compile on mac for iOS, thank you ___ Freetype mailing list Freetype@nongnu.org

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Sun, 6 May 2018 22:07:53 +0200, Gregor Mückl wrote: > On 5/6/2018 9:56 PM, Lawrence D'Oliveiro wrote: > >> On Sun, 6 May 2018 09:47:19 +0200, Gregor Mückl wrote: >>> >>> Also, on the way up to the exception handler in main(), stack >>> unwinding causes destructors of various objects to be

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Gregor Mückl
On 5/6/2018 9:56 PM, Lawrence D'Oliveiro wrote: On Sun, 6 May 2018 09:47:19 +0200, Gregor Mückl wrote: The important part here is that the constructor of gltb::Error records the actual runtime callstack of where it was executed, that is, how the throw statement was reached in the exection flow

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Sun, 6 May 2018 09:47:19 +0200, Gregor Mückl wrote: > The important part here is that the constructor of gltb::Error > records the actual runtime callstack of where it was executed, that > is, how the throw statement was reached in the exection flow of the > program. And its asFormattedText

Re: [ft-devel] [PATCH] Further fix to visibility flag testing with Solaris Studio compilers

2018-05-06 Thread Alan Coopersmith
On 05/ 6/18 10:24 AM, Alexei Podtelezhnikov wrote: >> AC_LINK_IFELSE does the compile and then tries to link the result... >> Signed-off-by: Alan Coopersmith > > Thank you, Alan. Wouldn't you want libtool to do it for you? There is > also IBM's -qvisibility and HP's

Re: [ft-devel] [PATCH] Further fix to visibility flag testing with Solaris Studio compilers

2018-05-06 Thread Alexei Podtelezhnikov
> AC_LINK_IFELSE does the compile and then tries to link the result... > Signed-off-by: Alan Coopersmith Thank you, Alan. Wouldn't you want libtool to do it for you? There is also IBM's -qvisibility and HP's -Bhidden. Most others define do -fvisibility and define

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Gregor Mückl
On 5/6/2018 10:15 AM, Lawrence D'Oliveiro wrote: On Sun, 6 May 2018 09:47:19 +0200, Gregor Mückl wrote: if(FT_Done_Face(face != 0) { You got to be kidding me. OK, there's a brace missing. That doesn't change anything I explained below.

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Lawrence D'Oliveiro
On Sun, 6 May 2018 09:47:19 +0200, Gregor Mückl wrote: > if(FT_Done_Face(face != 0) { You got to be kidding me. ___ Freetype mailing list Freetype@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] FT_Done_Face Should Not Return An Error

2018-05-06 Thread Gregor Mückl
On 5/6/2018 1:19 AM, Lawrence D'Oliveiro wrote: On Sun, 6 May 2018 00:11:12 +0200, Gregor Mückl wrote: Just don't assume that you know better than the creator of the host program when it is okay to bail and how to do so. As the provider of the lower-level abstraction, you guarantee certain