break appeared early in SER; so, it remained.<br>drop is a tad newer (?) and probably appeared in the tradition of packet filtering naming. there is also the more intuitive &quot;exit&quot; alternative to it.<br>there is also a &quot;return&quot; alternative for break.
<br><br>WL.<br><br><div><span class="gmail_quote">On 8/6/07, <b class="gmail_sendername">SIP</b> &lt;<a href="mailto:sip@arcdiv.com">sip@arcdiv.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Weiter Leiter wrote:<br>&gt;<br>&gt;<br>&gt; On 8/6/07, *tzieleniewski* &lt;<a href="mailto:tzieleniewski@o2.pl">tzieleniewski@o2.pl</a><br>&gt; &lt;mailto:<a href="mailto:tzieleniewski@o2.pl">tzieleniewski@o2.pl</a>&gt;&gt; wrote:
<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Hi,<br>&gt;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Is there any difference in the brake and drop command behavior in<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp; ser.cfg??<br>&gt;<br>&gt;<br>&gt; break stops execution of current route, resuming the next outer one
<br>&gt; (if any), from where the current was invoked.<br>&gt; drop stops execution of script.<br>&gt;<br>&gt; WL.<br>I&#39;m assuming these are SER 2.0 commands?<br><br>Is it possible to have come up with even more convoluted and
<br>non-intuitive names? Perhaps &quot;frog&quot; and &quot;bunny&quot;&nbsp;&nbsp;or &quot;seratonin&quot; and<br>&quot;cuisinart&quot; ?&nbsp;&nbsp;I mean, why stop with &#39;brake,&#39; which is so close to being<br>&#39;break&#39; (the command one usually uses in a programming setting to escape
<br>a loop) and yet... isn&#39;t. Or drop... which really doesn&#39;t imply to me<br>&#39;stop execution&#39; as much as it implies ignore an incoming connection...<br>or perhaps delete a table.<br><br>N.<br></blockquote>
</div><br><br clear="all"><br>-- <br>&quot;C is a language that combines all the elegance and power of assembly language with all the readability and maintainability of assembly language.&quot;