Boost C++ Libraries: Ticket #10385: init_from_stream ignores errors in config file/stream https://svn.boost.org/trac10/ticket/10385 <p> Some typos are ignored by the <code>boost::log::init_from_stream</code> function. </p> <p> For example config file with incorrectly spelled <code>Sinks.</code>: </p> <pre class="wiki">[Sink.ImportantSink] </pre><p> will be accepted and the whole section will be silently ignored. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10385 Trac 1.4.3 Andrey Semashev Wed, 20 Aug 2014 13:57:56 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/10385#comment:1 https://svn.boost.org/trac10/ticket/10385#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> Technically, this is a correct config with section Sink and a nested section <a class="missing wiki">ImportantSink</a>. The library simply doesn't use that section, but that doesn't make the config incorrect. I don't think that issuing errors upon any unrecognized sections or parameters is a good idea because they can potentially be used by the user. </p> Ticket Antony Polukhin Wed, 20 Aug 2014 14:12:46 GMT <link>https://svn.boost.org/trac10/ticket/10385#comment:2 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10385#comment:2</guid> <description> <p> How about providing an option for forcing strict/non-strict config file parsing, like it is done in <a href="http://www.boost.org/doc/libs/1_56_0/doc/html/program_options/howto.html#idp344642720">Boost.ProgramOptions</a>. </p> <p> Having it set so "strict" by default will help beginners to find errors in their config files, while advanced users still will be able to put all the configs in one file. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Andrey Semashev</dc:creator> <pubDate>Wed, 20 Aug 2014 15:47:42 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/10385#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10385#comment:3</guid> <description> <p> Having an optional strict mode might be useful, although it may affect public interfaces for extending the library. I'll have to think about it. In any case, I don't think it should be the default because the current behavior is different. </p> </description> <category>Ticket</category> </item> </channel> </rss>