[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ft] Future API (was Re: Faster computation of text width?)
From: |
Lawrence D'Oliveiro |
Subject: |
[ft] Future API (was Re: Faster computation of text width?) |
Date: |
Sat, 21 Mar 2015 09:18:59 +1300 |
On Wed, 18 Mar 2015 11:54:33 +0100 (CET), Werner LEMBERG wrote:
> There are ideas to provide a lighter interface for a
> forthcoming FreeType 3, but this won't come quickly.
Let me add a couple of suggestions for this:
* Dispose calls (FT_Done_Face etc) should accept a NULL pointer arg and
do nothing, like the libc free(3) call does. This makes it easier to
do unconditional cleanup of partially-allocated objects.
* FT_Reference_xxx calls should return the pointer that was passed to
them, like Cairo does. This way you can access an object and allocate
a reference to it in a single expression, e.g.
my_ref = reference(get_obj(whatever));
- Re: [ft] Faster computation of text width?, (continued)
- Re: [ft] Faster computation of text width?, Werner LEMBERG, 2015/03/13
- Re: [ft] Faster computation of text width?, John Found, 2015/03/13
- Re: [ft] Faster computation of text width?, Lawrence D'Oliveiro, 2015/03/13
- Re: [ft] Faster computation of text width?, Werner LEMBERG, 2015/03/14
- Re: [ft] Faster computation of text width?, John Found, 2015/03/14
- Re: [ft] Faster computation of text width?, Werner LEMBERG, 2015/03/18
- Re: [ft] Faster computation of text width?, John Found, 2015/03/18
- Re: [ft] Faster computation of text width?, Werner LEMBERG, 2015/03/18
- Re: [ft] Faster computation of text width?, Lawrence D'Oliveiro, 2015/03/18
- Re: [ft] Faster computation of text width?, Werner LEMBERG, 2015/03/18
- [ft] Future API (was Re: Faster computation of text width?),
Lawrence D'Oliveiro <=
- Re: [ft] Faster computation of text width?, Lawrence D'Oliveiro, 2015/03/18
- Re: [ft] Faster computation of text width?, John Found, 2015/03/18