<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I would agree here with Junxiao. We already made a decision before to treat unknown section as an error, and we should keep the consistency in implementation.</div><div><br></div><div>For now, we can add a dummy processor for generic section. Actually, word 'general', 'generic', or something else would be better than 'process'</div><div><br></div><div>---</div><div>Alex</div><br><div><div>On Mar 11, 2014, at 10:39 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Dear folks<div><br></div><div>I disagree. Nobody reads warnings.</div><div><br></div><div>An unknown section/field usually means there's a token is misspelled.</div><div>Continue processing leads to undesired behavior.</div>
<div><br></div><div><div class="gmail_extra">Yours, Junxiao<br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 10:16 PM, Davide Pesavento <span dir="ltr"><<a href="mailto:davidepesa@gmail.com" target="_blank">davidepesa@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<br>
</div>For better forward and backward compatibility, I think we should just<br>
print a warning, not throw an exception, upon encountering unknown<br>
config sections or fields.<br>
<br>
--<br>
Davide<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote></div></div></div></div>
_______________________________________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br></blockquote></div><br></body></html>