[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNUe-dev] Creating a system for debug-levels
From: |
Johannes Vetter |
Subject: |
Re: [GNUe-dev] Creating a system for debug-levels |
Date: |
Thu, 10 Feb 2005 14:10:23 +0100 |
Hi,
it's ok for me, except your level 3. shouldn't this (sql-commands) go
into a common level too ? for example a function in forms (level 4)
generates some sql-command on the backend (level 3).
depreciation warnings:
using level 1 for this is ok, but what about a function like
"gDepreciate (message)" ? if we would use 'gDebug ()' to print
depreciations they would not be seen on stdout. using an explicit
function for this could handle both, dumping to a given debug-level as
well as printing to stdout/stderr or something similair.
Thanks,
Johannes
Am Donnerstag, den 10.02.2005, 11:04 +0100 schrieb Reinhard Mueller:
> Hi all,
>
> AFAICT, so far the debug levels uses have not much of a system.
>
> How about something like:
> 1: Warnings like depreciation etc. - things that shouldn't happen when
> everything was perfect
> 2: reserved for temprorary debugging
> 3: SQL commands sent to the backend, or similar information for non-SQL
> backends
> 4-6: can be used by the tools, like forms, reports, appserver
> 7-9: can be used by common
>
> What would others think about this?
>
> Thanks,
> Reinhard
> _______________________________________________
> Gnue-dev mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnue-dev