Re: [boost] [Review] The review of the Boost.Logging library startstoday, November 7th

From: Paul A Bristow (pbristow_at_[hidden])
Date: 2005-11-08 10:51:53

| -----Original Message-----
| From: boost-bounces_at_[hidden] 
| [mailto:boost-bounces_at_[hidden]] On Behalf Of Hartmut Kaiser
| Sent: 06 November 2005 20:02
| To: boost_at_[hidden]
| Subject: [boost] [Review] The review of the Boost.Logging library starts
today, November 7th

1  I have started to review this very promising looking library, but am
deterred from trying it fully by the hassle of building the library.

(I have yet to get bjam to work well for me, and 2 lines in the bjam file
looks ominous

       <include>D:/boost/boost_latest/boost/  # FIXME remove this!

as I use I:\boost_root\.

I would persevere if I was confident I would use it - and I wasn't just
going to upgrade for VS 8.0 beta2 to VS 8.0 ;-)

I need:

boost_log-vc80-mt-gd-1_33.lib

and

boost_log-vc80-mt-1_33.lib

Could these be provided ready built for VS 7.1 and 8.0, 8.0 beta2 even?
(For the convenience of the idle/incompetent - and until bjam/v2 and its
documentation works foolproofly - 1.34?).

(As promised in the documentation, building the sources each time is rather
time-consuming to be practicable for real-life use).

2  I got several "warning C4996: 'localtime' was declared deprecated"
which should be suppressed IMO, until a better global 'solution' has been
adopted.

#  pragma warning(disable: 4996) // ' ' was declared deprecated.

3  Starting the simple example with the normal Ctrl F5 "start without
debugging", the console window starts with:

"CMD.EXE was started with
'\\hetp3\i$\boost_root\libs\log\examples\simple\vc71
as the current directory path.

UNC paths are not supported.  <<<<<<<<<<<<<<<<<<<<<<<<< ??????????????????

Defaulting to Windows directory. <<< <<<<< I wasn't clear what this meant,
so searched,
finding out.txt (with sensible contents) in C:/winnt - slightly to my
surprise!

15:10:11 [app] [Thread 2300] pre-start - this gets logged too!
15:10:11 [app.dbg] debug pre-start - this gets logged too!
<snip>

One the other hand using autostart as a post-build event
(a MUCH more convenient method of starting console applications
with Post build command line:

"$(TargetDir)\$(TargetName).exe" --result_code=no --report_level=detailed
--catch_system_errors=no

and description Autorun "$(TargetDir)$(TargetName).exe"

------ Rebuild All started: Project: vc71, Configuration: Release Win32
------
Deleting intermediate and output files for project 'vc71', configuration
'Release|Win32'
Compiling...
main.cpp
log_manager.cpp
log.cpp
functions.cpp
Generating Code...
Linking...
Embedding manifest...
Autorun
"\\hetp3\i$\boost_root\libs\log\examples\simple\vc71\release\vc71.exe" 
15:43:06 [app] [Thread 1448] pre-start - this gets logged too!
15:43:06 [app.dbg] debug pre-start - this gets logged too!
15:43:06 [app] [Thread 1448] testing1-2-3
15:43:06 [app.dbg] this is a debug message, i=1
15:43:06 I just wanted to tell you something....
15:43:06 [app.warn] Logged-on Users approach max. limit
15:43:06 [app.err] Too many users!
15:43:06 Creating main window
15:43:06 A debug msg coming from {charts} module
15:43:06 Destroying main window
15:43:06 [app] [Thread 1448] However, this msg. will
15:43:06 [app.dbg] this will be written - this log just got enabled
15:43:06 [app.err] this will be written - all logs are enabled
15:43:06 [app.dbg] this will be written
15:43:06 a simple info
Build log was saved at
"file://\\hetp3\i$\boost_root\libs\log\examples\simple\vc71\Release\BuildLog
.htm"
vc71 - 0 error(s), 0 warning(s)
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

and out.txt is at

\\hetp3\i$\boost_root\libs\log\examples\simple\vc71\out.txt

as expected.

But overall looking good :-)

Thanks.

Paul

-- 
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
Phone and SMS text [phone], Mobile and SMS text [phone]
mailto: pbristow_at_[hidden]  www.hetp.u-net.com