<br><br><div class="gmail_quote">On Mon, Nov 23, 2009 at 9:55 AM, Tzafrir Cohen <span dir="ltr"><<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Mon, Nov 23, 2009 at 02:12:37PM -0200, Daniel Ferrer wrote:<br>
> From branches/1.4/doc/ael.txt:<br>
><br>
> "There are a subset of checks that have been removed until the proposed<br>
> AAL (Asterisk Argument Language) is developed and incorporated into<br>
> Asterisk.<br>
> ...<br>
> * Calls to applications not in the "applist" database (installed<br>
> in /var/lib/asterisk/applist" on most systems)<br>
> ...<br>
> "<br>
> Is there some progress on this? Last code I've seen is 3 years old from<br>
> murf here:<br>
> <a href="http://svnview.digium.com/svn/asterisk/team/murf/AAL/" target="_blank">http://svnview.digium.com/svn/asterisk/team/murf/AAL/</a><br>
><br>
> Any other AAL update? What's the situation of AAL in trunk?<br>
<br>
</div>The list of valid apps depends on the loaded modules. Is that intended<br>
for off-line tests?<br></blockquote><div><br>That's the problem!<br><br>I did AAL as I was working on AEL, because I thought it would be really cool if we could<br>check the args to each app, and make sure they are sane; some options (especially 'j')<br>
are really, really, not good to use with AEL. But AAL kinda died the death, because I saw<br>no easy way to gather the necessary info, and it was a static list. What we would need <br>would be a dual standard: both gatherable from loaded modules, and gatherable offline,<br>
when asterisk is not running, from the source itself, if at all possible. This kinda thing<br>would require a unified format for the description of arguments; something that could be<br>derived from the source at build time. And, some way to collect this info for add-on apps<br>
that aren't in the main source tree, but added onto asterisk by one means or another.<br><br>Well, in the following years, some good things have happened... we have the xml <br>app and func interface descriptions now, which seem to provide most of the info<br>
we would need for something like AAL. The arg parsing for apps has been unified,<br>which would be another step. So, maybe AAL could be adapted to the new environmnet<br>somehow.<br><br>murf<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
--<br>
Tzafrir Cohen<br>
icq#16849755 <a href="mailto:jabber%3Atzafrir.cohen@xorcom.com">jabber:tzafrir.cohen@xorcom.com</a><br>
+972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br>
<a href="http://www.xorcom.com" target="_blank">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir" target="_blank">iax:guest@local.xorcom.com/tzafrir</a><br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Steve Murphy<br>ParseTree Corp<br><br>