Hi,
> >> Could you not go with standard iostreams for log4cxx then?
no we couldn't go with standard iostreams as this would restrict
customers who are using classic iostreams
> I believe you can get around this limitation by using STLport iostreams
Introducing STDport is not ideal for us as it's a further 3rd party
lib which customers may also be using and adds further risk to version
clashes etc. This could be circumvented I know, but I also know people
here with strong opinions that the combined use of ??printf and a good
String/StringBuffer class with streaming operators is the only way to
go.
Our experience with providing libs to customers led us to remove
iostreams completely from our products as their presence led to far
too many build & packaging cimplications. I was hoping that this
experience was shared by log4cxx and it would be mutually beneficial
for us to remove them. Given that log4cxx doesn't provide a binary
distribution I can see why this isn't really an issue and so using
iostreams gives all the benifits without the (our) drawbacks.
Anyway thanks for all your time & input.
Regards,
Ken.
