Re: Logging Library-GSOC

[Priyesh kumar]

> I could only come up with another set of
> tracing macros like `FT_TRACEC[0-7]` ('C' for continuing) that don't
> emit a final newline. 

This is a better solution as with it we don't have to do extra comparisons...

But since time is not a constraint here, this won't be necessary,

I have added some changes to produce the desired output using the previous approach specified by you.

With this approach, I have to make very little changes in some FT_TRACE calls for better indentation. 

Would that be OK with you?

I am attaching a log file generated by the ftview.c demo program representing the new changes...

Please guide me...

Thanks,

Priyesh

On Mon, Jul 6, 2020 at 11:53 AM Werner LEMBERG <wl@gnu.org> wrote:

> > Since debugging isn't time critical it might be necessary to add
> > an additional step that scans tracing messages for newline
> > characters, then massaging the output by inserting the time stamp.
> > In other words, all occurrences of `\n` should be replaced with
> > `\n[time stamp] ` or something similar.
>
> I also came up with the same idea but thought that string comparison
> will take plenty amount of time, therefore, I dropped this idea...
> But, as you said so I will try to implement it...

Do you have a better idea?  I could only come up with another set of
tracing macros like `FT_TRACEC[0-7]` ('C' for continuing) that don't
emit a final newline.  This would imply *a lot* of (mostly mechanical)
changes in the source code.  It wouldn't really uglify the source
code, though, but I think a solution that doesn't necessitate this
distinction is preferable since easier to use.


    Werner

freetype2.log
Description: Text Data