Strings and configuration (unrelated to each other)
Hello! I have two questions about the log4cxx API. First of all, when I configure log4cxx in the following way: log4cxx::PropertyConfigurator::configure(string(/usr)); it fails silently. Is this the way it is supposed to behave? I would have preffered it to say something similar to what it says when I point it to a file that edoes not exist. My second question is about the String class. In the examples I have seen strings are constructed with _T(). Where is this function declared? Where is String declared? Will it be OK for me to send strings to log4cxx using std::string? Thanks in advance! Regards, Mattias
Re: Strings and configuration (unrelated to each other)
Mattias Brändström a écrit : Hello! I have two questions about the log4cxx API. First of all, when I configure log4cxx in the following way: log4cxx::PropertyConfigurator::configure(string(/usr)); it fails silently. Is this the way it is supposed to behave? I think so. I would have preffered it to say something similar to what it says when I point it to a file that edoes not exist. My second question is about the String class. In the examples I have seen strings are constructed with _T(). Where is this function declared? This is a macro used by gettext for internationalisation. cf gettext documentation for more information. Where is String declared? helper/tchar.h: 310 typedef std::basic_stringTCHAR String; Will it be OK for me to send strings to log4cxx using std::string? Yes, if TCHAR is a char, then String is equivalent to std::string. Regards, -- Christophe de Vienne
Re: Strings and configuration (unrelated to each other)
On Sep 3, 2004, at 3:56 AM, Mattias Brändström wrote: Hello! I have two questions about the log4cxx API. First of all, when I configure log4cxx in the following way: log4cxx::PropertyConfigurator::configure(string(/usr)); it fails silently. Is this the way it is supposed to behave? I would have preffered it to say something similar to what it says when I point it to a file that edoes not exist. Don't know that one off the top of my head My second question is about the String class. In the examples I have seen strings are constructed with _T(). Where is this function declared? Where is String declared? Will it be OK for me to send strings to log4cxx using std::string? I've been assigned to rework the Unicode support and will dive into as soon as I finish my current project. The bug report (http://nagoya.apache.org/jira/browse/LOGCXX-10) has more details. _T is a preprocessor macro defined in log4cxx/helpers/tchar.h (patterned after Windows tchar.h) that wraps the string literal with a L so make it a long string literal if UNICODE is defined. Currently log4cxx only supports logging Unicode or MBCS, in my rework, it can support both simultaneously. I expect to remove the _T macro from log4cxx (since it can be inconsistent with the Windows tchar.h definition) and would avoid using it in new code. String is an alias for std::string unless UNICODE is set when it is an alias for std::wstring. So if you pass char* or std::string's to log4cxx, you should see no changes when I've finished the Unicode rework.
use of log4cxx on multiple platforms...
Hi, I am new to this log4cxx user group. I have few questions regarding usage of log4cxx on multiple platforms. We have a product that runs on different platforms. We need some logging mechanism so that we can use on different platforms. Our product runs on Windows, MVS, Sun Solaris, AIX and Linux. I read about log4cxx and was very excited and thought we could use that in our project. I have read some of the mails in the mailing list archives and have few questions before I start using this product. 1. I see that the standard release of this product is not yet released. So is it ok to use it in my project? 2. I see that there are some issues running on solaris and AIX. So I am not sure whether to go for this product or use our own logging mechanism. 3. We have implemented multi tasking in our project. (multile processes and NOT multiple threads). So if I use this logging product, will I be able to consolidate my messages from different processes? 4. When will this product be tested on solaris and AIX? 5. When is the standard release of this product expected? Please give your suggestions on this. Thank you very very much, -Mike B. Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now.
Re: use of log4cxx on multiple platforms...
Mike We use it on: Windows Solaris Linux These are for real-time, production systems which we've guaranteed 99.999% uptime... (though I guess a single module crashing wouldn't affect the up-time). Renny Koshy President CEO RUBIX Information Technologies, Inc. www.rubixinfotech.com Mike SG [EMAIL PROTECTED] 09/03/2004 02:54 PM Please respond to Log4CXX User To:log4cxx-user@logging.apache.org cc: Subject:use of log4cxx on multiple platforms... Hi, I am new to this log4cxx user group. I have few questions regarding usage of log4cxx on multiple platforms. We have a product that runs on different platforms. We need some logging mechanism so that we can use on different platforms. Our product runs on Windows, MVS, Sun Solaris, AIX and Linux. I read about log4cxx and was very excited and thought we could use that in our project. I have read some of the mails in the mailing list archives and have few questions before I start using this product. 1. I see that the standard release of this product is not yet released. So is it ok to use it in my project? 2. I see that there are some issues running on solaris and AIX. So I am not sure whether to go for this product or use our own logging mechanism. 3. We have implemented multi tasking in our project. (multile processes and NOT multiple threads). So if I use this logging product, will I be able to consolidate my messages from different processes? 4. When will this product be tested on solaris and AIX? 5. When is the standard release of this product expected? Please give your suggestions on this. Thank you very very much, -Mike B. Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now.
