[Gegl-developer] Gegl logging statements

[Henrik Akesson]

Hi,

I tend to sprinkle the code with logging statements when learning/debugging.
glib has the appropriate functionality for managing the logs... Normally the
overhead of the logging statements (if turned off) is neglectable.

Should I leave my log statements in my patches (that will be mainly focused
on adding comments)?

Example statement:

  g_debug ( {%s:%u} rectangle split to (%ux%u) and (%ux%u)\n,
  __FILE__, __LINE__, dr-height, dr-width,
  fragment-height, fragment-width);
Output:

** (lt-gegl:13884): DEBUG: {gegl-processor.c:460} rectangle split to
(675x496) and (675x256)


Thanks,

Henrik
___
Gegl-developer mailing list
Gegl-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer

Re: [Gegl-developer] Gegl logging statements

[Martin Nordholts]

Henrik Akesson wrote:
 Should I leave my log statements in my patches (that will be mainly
 focused on adding comments)?

Hi,

Please leave them in the patches. I've always wanted more debug logging
in GEGL and it is easy to later remove the ones that give noticeable
performance hits

BR,
Martin
___
Gegl-developer mailing list
Gegl-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gegl-developer