[Asterisk-Dev] Dev Meeting list

[Eric Wieling aka ManxPower]

Eric Wieling aka ManxPower wrote:

> alex at pilosoft.com wrote:
> 
>> On Thu, 28 Apr 2005, John Todd wrote:
>>
>>
>>> Interesting method, but not quite consistent across all applications
>>> considering many applications have many arguments they take, and adding
>>> priorities into the argument list seems a bit "busy".  Here's a rehashed
>>> message from long ago (and look!  I even used ENUM as the example!) -
>>> perhaps it may be of some use in this thread:
>>
>>
>> Am I the only one who has horrible flashbacks of both BASIC (numbered 
>> code) and FORTRAN (computed GOTOs) at same time?
>> Ugh. I think by now everyone should realize that line-numbered 
>> programming
>> is so 20th century. ;)
>>
>> No, I'm not volunteering to replace asterisk dialplan with Yet Another 
>> Embedded Language ;)
> 
> 
> I'm a big fan of this (I use it in my macros and AGIs):
> 
> 1) Set some variables to pass things/settings/informstion to the 
> application
> 
> 2) Run the application
> 
> 3) Check the variables that the application sets to get information from 
> the application.
> 

Replying to myself.  Most apps seem to go to pri+1 if they want to go 
to pri+101, but it doesn't exist.  Seems pretty simple to have the 
apps set variables to communicate with the rest of the dialplan and 
not break existing dialplans.  Also seems pretty easy to have apps 
check for dialplan variables and using those if they don't see any 
parameters when they are called.  This also doesn't break existing 
dialplans.

-- 
Always do right. This will gratify some people and astonish the rest.
Mark Twain