Lightweight version of configuration files

[gregoire]

I like and use a lot Poco::Util::IniFileConfiguration and Poco::Util::PropertyFileConfiguration.

In some cases I would like to use them in a lightweight version: without AutoPtr, AbstractConfiguration, etc
So is it possible to extract code from Poco::Util::IniFileConfiguration to create Poco::Util::IniFile ?

Poco::Util::IniFile could be used in many cases, Poco::Util::IniFileConfiguration would be one of them.

What do you think ?

[aderouineau]

What makes the use of AutoPtr "so heavy" ?

[gregoire]

I will try not to feed the troll about AutoPtr, shared_ptr, etc: I like them, use them when I need them, etc.

However I think that there are times and places for smart pointers.

In my case, I developp an API which uses shared_pointer and weak_pointer to manage some inter-linked objects.
If I want to use and store a Poco::Util::IniFileConfiguration, I will somewhere have a shared_pointer of an AutoPtr that will never be duplicated. I think it would not be such a good design.

Other use case: I write a single threaded application on Linux. If I use AutoPtr I think that I will have to link my application to pthreads, since AtomicCounter will use a FastMutex.

I agree that most of the times, smart pointers is handy and usefull but why not let the user choose ?