X-Received: by 10.224.189.78 with SMTP id dd14mr7433920qab.0.1359345464426; Sun, 27 Jan 2013 19:57:44 -0800 (PST) X-Received: by 10.49.116.139 with SMTP id jw11mr2162873qeb.12.1359345464401; Sun, 27 Jan 2013 19:57:44 -0800 (PST) Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!p13no5707026qai.0!news-out.google.com!k2ni2734qap.0!nntp.google.com!p13no5707017qai.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.java.programmer Date: Sun, 27 Jan 2013 19:57:44 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=217.172.23.24; posting-account=Z-5a_wkAAABTzN1pAiC7xNW_xfTNp2Vr NNTP-Posting-Host: 217.172.23.24 References: <0cfefb99-94f9-44e0-9b58-926818a9560d@googlegroups.com> <78bfbd4c-a257-44ed-ae03-73ceb19fab18@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: ultralog: new concept of logging API From: Mikhail Vladimirov Injection-Date: Mon, 28 Jan 2013 03:57:44 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: csiph.com comp.lang.java.programmer:21815 > Actually, I disagree with both claims, but regardless, even if you > prefer the first version, I fail to see the advantage in your way of > doing it compared to just doing this: When I read the code which logs something, what I usually need to know, is = what information is logged here and which level at. I may need to know thi= s because I'm doing code review and I want to make sure that proper informa= tion is logged at proper levels. Also I may need this during issue investi= gation because I don't see something in the log that logically should be th= ere and I want to make sure that I didn't forget to put logging in the code= . I usually don't care about exact words and commas in the log message. O= nly what information is logged and which level at. The real cases when I need to know log message literally, are: 1. I want to review all log message to make sure they obey our policy regar= ding style, formatting and levels. 2. I found something in the log and I need to find place in code where it w= as logged. The later two things are hard to do when log messages are spread among the = code and are written in the form of concatenations. Especially hard is to = find in the code log messages that was taken from log file if you don't kno= w exactly which parts of the message are hardcoded and which parts were sub= stituted from variables. Anyway, the idea of ultralog was to offer garbage-free yet clear syntax, no= t syntax that is clearer than even non garbage-free ones.