NoBug logging flag hierachy =========================== [options="autowidth"] |==================================== |*State* | _Final_ |*Date* | _2008-04-05_ |*Proposed by* | ct |==================================== NoBug logging flag hierachy --------------------------- https://nobug.pipapo.org/[NoBug] allows hierachical organization of logging flags. Propose a documentation/planning about the setup. Description ~~~~~~~~~~~ Take a look at my draft at: https://git.lumiera.org/?p=LUMIERA;a=blob;f=doc/devel/nobug_flags.txt;h=325141acb52a7be7f75425359b6057c74ed30253;hb=a03e3c5e73a4c0be2264ac4e4e0f02eb8749837b[nobug_flags.txt] I've added the things I planning for the backend, others might add their own plans there too. So far this is an early draft, comments welcome. NOTE: outdated information. Have a look at `include/logging.h` Tasks ~~~~~ * Needs a file.c defining the common root see link:{rfc}/GlobalInitialization.html[RfC: Global Initialization] * Everyone needs to setup this hierachy by `NOBUG_DEFINE_FLAG_PARENT (flag, parent_flag);` Pros ~~~~ When done right, logging control is much easier, just 'NOBUG_LOG=lumiera:DEBUG' would suffice. Rationale ~~~~~~~~~ We need some easy way to control logging, later on when lumiera runs in beta tests it must be easy to tell a tester how to create useable debugging logs. Comments -------- //comments: append below cehteh will care for further integration ct:: '2008-07-26T09:11:29Z' The basic idea is still valid, but information in this RfC is quite outdated. Meanwhile, we have a somewhat different and largely extended log hierarchy. And it turned out, that it isn't practical to scatter the NOBUG_FLAG_PARENT definitions all over the code base. Rather, we use a single include file `include/logging.h` to define all flags in a systematic way Ichthyostega:: 'Di 29 Okt 2013 05:52:34 CET' ~~ //endof_comments: '''' Back to link:/x/DesignProcess.html[Lumiera Design Process overview]