<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2176/25/9/_/styles/combined.css?spaceKey=AST&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/AST/Using+the+Configuration+Framework">Using the Configuration Framework</a></h2>
<h4>Comment <b>removed</b> by <a href="https://wiki.asterisk.org/wiki/display/~lathama">Andrew Latham</a>
</h4>
<br/>
<div class="notificationGreySide">
<p>That's not the case. The issue is one of severity: if a module cannot load itself, it should return DECLINE if the system can reasonably function without the module. If the module cannot load itself and the system cannot function - or should not function - without the module, it should return FAILURE.</p>
<p>Crafting a one size fits all policy isn't a good idea. Rather, module writers should use common sense about what a user would most likely want when an error condition occurs, and write their module appropriately. (Also, module return codes is not the purpose of this wiki page.)</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=AST">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>