> OK. What about passing `__LINE__` then?
Alright, I have done the relevant changes, to pass
line through a function parameter I had to change
`FT_DEBUG_INNER' and `FT_ASSIGNP_INNER'
macros like this:
```
#define FT_DEBUG_INNER( exp ) ( _ft_debug_file = __FILE__, \
Hi, sorry for lack of responses. I have been very busy with final projects
for my summer classes and to top it off, some of the ram (or slots on the
motherboard) in my computer died and my computers were super wonky until I
figured out the cause. I have however been working on this as much as time
Hello Moustapha,
> I'm Mr Kourouma Moustapha, i used to use N'KO as language in Ubuntu.
> I have already installed ttfautohint (see below) but i don't find
> nkoo nor N'KO in the list of languages available.
>
> :~$ sudo aptitude search ttfautohint
>
> p libttfautohint-dev - Automatic
Hi Werner,
As suggested by you I have used `setvbuf()` function in `FT_Message()`
function
for printing logs on stderr in Full buffering mode when
FT_DEBUG_LEVEL_TRACE macro
is enabled.
For FT2_DEBUG=any:7 and command:
main.exe arial.ttf *qwertyuiopasdfghjklzxcvbnm *
I have got the following
*> This still looks fishy.*
Ok, I will try `setvbuf()` function :D
*> Probably yes. At least the difference between the two approaches>
shouldn't be *that* large, I believe.*
*> Well, for comparison purposes the buffering mode should be the same> for
`FT_LOGGING` and `FT_DEBUG_LEVEL_TRACE*
> When I am redirecting stderr logs to a text file using: `main
> arial.ttf qwertyuiopasdfghjklzxcvbnm 2>sdterr_logs.txt` I am getting
> the following results:
>
> `FT_LOGGING`: 8 sec
> `FT_DEBUG_LEVEL_TRACE`: 11 sec
This still looks fishy.
>> Otherwise I guess the big difference between
>> Having two versions would also allow to use a function internally
>> so that you can (a) avoid the `do {} while (0)` construction, and
>> (b) still use the macro within a conditional.
>
> I thought about that, but if we create a function then the memory
> dump won't print the actual line
> There should be zero overhead for the non-debugging case.
> Having two versions would also allow to use a function internally so
> that you can (a) avoid the `do {} while (0)` construction, and (b)
> still use the macro within a conditional.
I thought about that, but if we create a function
Hi Werner,
*> This looks very unrealistic. Do you redirect data sent to stderr to> an
output file?*
No, I haven't redirected the data sent to stderr to an output file, for
measuring time : (
I thought I have to use the time value which I got when data from stderr is
not sent to a .txt file
> I have tried the query performance counter/frequency method for
> example program:
> (https://www.freetype.org/freetype2/docs/tutorial/example1.c) on
> Windows with arial.ttf and FT2_DEBUG=any:7 on
> string:"qwertyuiopasdfghjklzxcvbnm" which produced 24260 logs.
>
> I have executed the test
10 matches
Mail list logo
