Re: [ft-devel] improved tracing support

[Werner LEMBERG]

>>   objs:3:     FT_Open_Face: Requesting number of faces and named instances
>>   io:1:       FT_Stream_Open: opened `arial.ttf' (273020 bytes) successfully
>>   ttobjs:2:   TTF driver
>>   sfobjs:2:     SFNT driver
>>   sfobjs:3:   sfnt_open_font: synthesize TTC
>>   sfobjs:2:   sfnt_init_face: 0x20aa9d0 (index -1)
>>   ttload:2:   tt_face_load_font_dir: 0x20aa9d0
>>   ttload:2:   -- Number of tables:         23
>>   ttload:2:   -- Format version:   0x00010000
> 
> It is ok, but a little bit redundant.

What exactly do you mean with `redundant'?  Sometimes, the tracing
output of `any:7' can be overwhelmingly large.  Currently, it's
tedious to find out how to explicitly trace a certain feature; it
normally means that you have to look up the source code to get the
right `FT2_DEBUG' argument.  With the above output it should be much
simpler.

>> To implement that, I would use variadic macro support introduced to
>> the C99 preprocessor – in case this is not available, the tracing
>> will look as of today.
> 
> __func__ is also useful in C99.  Imagine how many function names we
> could hide.  That would require C99 for tracing.

Well, yes, but we would lose a lot of tracing information for older
compilers that don't support `__func__'.

> I see a lot of 0x%X, which can be shortened to %#X, crazy of me to
> even mention.

Since this is a standard `printf' feature it could be changed any
time.


    Werner