| to ,

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What's up with the conversions for delimiter from | to ,?

Is this something we should pay attention to or just in
documentation?

- --
Cheers,

Matt Riddell
Director
_______________________________________________

http://www.venturevoip.com
 (Great new VoIP end to end solution)
http://feeds
.feedburner.com/AsteriskNews (Daily Asterisk News -
rss)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFGefwLDQNt8rg0Kp4RAoi3AJ9k4jJ2sYLtY4Bp88GFLTfvih4TSwCf
eGVU
qCCByT72fXz0UfG6C+OlKF0=
=k+70
-----END PGP SIGNATURE-----

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

On Wednesday 20 June 2007, Matt Riddell wrote:
> What's up with the conversions for delimiter from | to
,?
>
> Is this something we should pay attention to or just in
documentation?

I assume you're talking about my dialplan_aesthetics
branch?

I'm going through and revamping the dialplan to reduce the
amount of escaping
we need to do in extensions.conf, and that includes this
change.  This should
hopefully make the dialplan less difficult to get right in
the future.

It's not quite done yet, but you're welcome to try it out
and give me
feedback.  It is at a state already where most things work
fine with no
changes, if you're already using "," as your
delimiter (which most people
are).

-- 
Tilghman

_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tilghman Lesher wrote:
> On Wednesday 20 June 2007, Matt Riddell wrote:
>> What's up with the conversions for delimiter from |
to ,?
>>
>> Is this something we should pay attention to or
just in documentation?
> 
> I assume you're talking about my dialplan_aesthetics
branch?

Yep 

> I'm going through and revamping the dialplan to reduce
the amount of escaping
> we need to do in extensions.conf, and that includes
this change.  This should
> hopefully make the dialplan less difficult to get right
in the future.

Ok, makes sense.

> It's not quite done yet, but you're welcome to try it
out and give me
> feedback.  It is at a state already where most things
work fine with no
> changes, if you're already using "," as your
delimiter (which most people
> are).

Will try it out on the next Asterisk box that comes online.

Anything I should look out for?  Anything expected to break
it?

- --
Cheers,

Matt Riddell
Director
_______________________________________________

http://www.venturevoip.com
 (Great new VoIP end to end solution)
http://feeds
.feedburner.com/AsteriskNews (Daily Asterisk News -
rss)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFGfx2jDQNt8rg0Kp4RArLiAKC6BiRgPuznp0nvrlrAYBt4icj3TgCf
WswG
xiqh3wZiUZhdrvloH0jv39Y=
=jmX+
-----END PGP SIGNATURE-----

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

On Sunday 24 June 2007, Matt Riddell wrote:
> Tilghman Lesher wrote:
> > It's not quite done yet, but you're welcome to try
it out and give me
> > feedback.  It is at a state already where most
things work fine with no
> > changes, if you're already using "," as
your delimiter (which most people
> > are).
>
> Will try it out on the next Asterisk box that comes
online.
>
> Anything I should look out for?  Anything expected to
break it?

Try lots of different things.  Really, the problem is that
we still have a ton
of things which still use non-standard parsing, and that
poses the greatest
challenge towards getting this conversion complete.

The other question, once this conversion is complete, is
whether it ought
to happen now or not.  Obviously, my position is that it
should, or I wouldn't
be doing this.  However, it is going to create a flag day,
where when you
upgrade to a certain revision, you're going to need to
remove quite a bit of
escaping from your dialplan to get it to work correctly. 
That may also pose
a bit of a problem when people upgrade from 1.4 to the
version following, as
we've always tried to maintain a position of "if you're
not using anything
deprecated, then upgrading to the next major release
shouldn't break your
dialplan."

This is progress, however, and making it easier at this
stage is going to
enable us to do more complex stuff in the future.

-- 
Tilghman

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

I see so many people still on 1.2.X, they will have the
fortune of
learning this and the updated variable and function options
all at
once....



On 6/24/07, Tilghman Lesher <tilghmanmail.jeffandtilghman.com> wrote:
> On Sunday 24 June 2007, Matt Riddell wrote:
> > Tilghman Lesher wrote:
> > > It's not quite done yet, but you're welcome
to try it out and give me
> > > feedback.  It is at a state already where
most things work fine with no
> > > changes, if you're already using
"," as your delimiter (which most people
> > > are).
> >
> > Will try it out on the next Asterisk box that
comes online.
> >
> > Anything I should look out for?  Anything expected
to break it?
>
> Try lots of different things.  Really, the problem is
that we still have a ton
> of things which still use non-standard parsing, and
that poses the greatest
> challenge towards getting this conversion complete.
>
> The other question, once this conversion is complete,
is whether it ought
> to happen now or not.  Obviously, my position is that
it should, or I wouldn't
> be doing this.  However, it is going to create a flag
day, where when you
> upgrade to a certain revision, you're going to need to
remove quite a bit of
> escaping from your dialplan to get it to work
correctly.  That may also pose
> a bit of a problem when people upgrade from 1.4 to the
version following, as
> we've always tried to maintain a position of "if
you're not using anything
> deprecated, then upgrading to the next major release
shouldn't break your
> dialplan."
>
> This is progress, however, and making it easier at this
stage is going to
> enable us to do more complex stuff in the future.
>
> --
> Tilghman
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.c
om--
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>


-- 
/*
 Andrew Latham
 LATHAMA (lay-th-ham-eh)
 lathamalathama.com
 lathamagmail.com
*/

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev