[Asterisk-Users] extension parser

[David C. Troy]

On this subject, please see bug #274 on bugs.digium.com; I think a common 
parsing mechanism should be developed, which could be used across all 
applications and within * itself.

http://bugs.digium.com/bug_view_page.php?bug_id=0000274

There is a lot of inconsistency about how parameters are specified and 
it's fairly fragile as written; also very easy for individual authors to 
make mistakes or do things differently from other authors.

Dave

=====================================================================
David C. Troy   [dave at toad.net]                   410-384-2500 Sales
ToadNet - Want to go fast?                        410-544-1329 FAX
570 Ritchie Highway, Severna Park, MD 21146-2925  www.toad.net

On Mon, 15 Sep 2003, Paul Crick wrote:

> On Monday 15 September 2003 19:49, Tais M. Hansen wrote:
> > Before I hack out the ',' -> '|' tr in extension.conf parser, any way to
> > escape ',' that I missed?
> 
> This sparked a thought with me and I've been meaning to delve through the
> docs and/or ask the question for a while now. What is the preferred way of
> doing extension.conf? I've seen some documentation that's in the format
> "1234,1,Command(opt|opt)" but other examples show it as
> "1234,1,Command,opt|opt" and it seems in a lot of places the command doesn't
> necessarily need the brackets ("Busy()" versus "Busy" for example)
> 
> I guess the parser makes a lot of options possible, but what is the
> preferred/defined syntax?
> 
> Cheers
> Paul
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
>