Re: [asterisk-users] Large dial plans and variables

2007-05-03 Thread Ira
At 09:29 AM 5/3/2007, you wrote: I guess we are. I propose we add functions or procedures! How about we just start over and make it a proper language? Not that I don't love it, but the hoops that one has to jump through because it's not cause my hair to disappear at an ever faster rate. Ira

Re: [asterisk-users] Large dial plans and variables

2007-05-03 Thread Doug Garstang
Andreas Sikkema wrote: You're so right! I thought about having just a catchall _. extension in the dialplan and doing everything else in a "real" language via AGI - PHP, Perl, ... whichever you like. It would make the programming part much easier as the scope of variables is just as you expect i

RE: [asterisk-users] Large dial plans and variables

2007-05-03 Thread Andreas Sikkema
> You're so right! > > I thought about having just a catchall _. extension in the > dialplan and doing everything else in a "real" language via AGI - > PHP, Perl, ... whichever you like. It would make the programming > part much easier as the scope of variables is just as you > expect it to be. W

Re: [asterisk-users] Large dial plans and variables

2007-05-02 Thread Doug Garstang
Philipp Kempgen wrote: Doug Garstang wrote: I have a large dial plan here with over 3000 lines, and several dozen macros. As it grew, it became apparent that there was some problems. 1. When you pass arguments to a macro in the form of $ARG1, $ARG2 etc, if that macro calls another macro,

Re: [asterisk-users] Large dial plans and variables

2007-05-02 Thread Philipp Kempgen
Doug Garstang wrote: > I have a large dial plan here with over 3000 lines, and several dozen > macros. As it grew, it became apparent that there was some problems. > > 1. When you pass arguments to a macro in the form of $ARG1, $ARG2 etc, > if that macro calls another macro, and passes argument

Re: [asterisk-users] Large dial plans and variables

2007-05-02 Thread Philipp Kempgen
Doug Garstang wrote: > I have a large dial plan here with over 3000 lines, and several dozen > macros. As it grew, it became apparent that there was some problems. > > 1. When you pass arguments to a macro in the form of $ARG1, $ARG2 etc, > if that macro calls another macro, and passes argument