> In my projects, I always set VS to the highest warning level (4). Poco behaves very well and is very quiet but there are many cases where a default constructor or equal operator cannot be generated (blocked at the parent level) and a warning is given.
> I would gladly go over the code and add those implemnetation-less private members to such classes to remove the warning.
I did a quick check of the Foundation classes with W4. No additional warnings here,
at least with VS8.0. I didn't test the other solutions though.
We are always looking for contributions and if you want to go over the
code, now would be a good time point with 1.3
being rather recent (and fewer warnings are always welcome).
Feel free to proceed and send me the changed files to email@example.com,
with x=peter, y=schojer.
Abut timeline: 1.3.1 will probably be released in about two weeks.
Do you want to wait for that release and then start or do you want
your changes to be part of 1.3.1?