===================================================================
RCS file: /usr/share/cvsroot/asterisk-ng/pbx.c,v
retrieving revision 1.24
diff -r1.24 pbx.c
833c833
< ast_log(LOG_DEBUG, "Ignoring, since number of digits to stirp is 0\n");
---
Quote:
ast_log(LOG_DEBUG, "Ignoring, since number of digits to strip is 0\n");
Another thing -- after looking at some of the included applications, I
came to the conclusion that C is not necessarily the best language to
write them in; As a result, I'm playing with adding support for
applications written in perl to be loaded and used by asterisk. More on
this after I actually get something that appears to work -- though if
anyone wants to comment or object, I'd appreciate hearing about it now.
Btw, if you offer non-anonymous CVS access (so I could just commit this
kind of thing rather than posting it to the list), I'd be appreciative.
--
Unsigned; For verification, send encrypted copy to cduffy@bigfoot.com.
Finger cduffy@ect-unix.csuchico.edu for OpenPGP key (1024D/734383C2).
Fingerprint: F3CB 38FD 8775 839A 5D46 F905 EA2E E169 7343 83C2
Not quite sure how I missed that one (duh!) Thanks!
Thanks for the spelling correctin, but I'm sure there are many more. I
should probably write a spell checker for C code if there isn't one
already.
Quote:
Another thing -- after looking at some of the included applications, I
came to the conclusion that C is not necessarily the best language to
write them in; As a result, I'm playing with adding support for
applications written in perl to be loaded and used by asterisk. More on
this after I actually get something that appears to work -- though if
anyone wants to comment or object, I'd appreciate hearing about it now.
For applications, yes, I think perl could be a logical choice, and indeed
I had started playing with creating a perl module based on Asterisk.
The area that I feel needs the most help in terms of scripting is the
creation of extensions. The format you see in
/etc/asterisk/extensions.conf, which closely matches the internal
representation, but that ws not the (only) representation that I wanted to
provide the user. There needs to be some sort of macro language, maybe
even a scripting language.
Quote:
Btw, if you offer non-anonymous CVS access (so I could just commit this
kind of thing rather than posting it to the list), I'd be appreciative.
I do have non-anonymous CVS. You can either send me patches off hte list,
or use CVS, but Unless you plan to make large changes (or large numbers of
changes), I'd rather just have you mail me patches to me personally to
apply at this point.
BTW, I'll be travelling back to the U.S. tomorrow and will likely be out
of e-mail contact for a day or so.
On Fri, Jan 07, 2000 at 02:22:15AM -0600, Mark Spencer wrote:
Quote:
> > if(!(out->data =3D malloc(fr->datalen + AST_FRIENDLY_OFFSET))) {
> > free(out);
=20
Not quite sure how I missed that one (duh!) Thanks!
=20
Thanks for the spelling correctin, but I'm sure there are many more. I
should probably write a spell checker for C code if there isn't one
already.
In emacs, "ispell-comments-and-strings" will do the trick.
Quote:
> Another thing -- after looking at some of the included applications, I
> came to the conclusion that C is not necessarily the best language to
> write them in; As a result, I'm playing with adding support for
> applications written in perl to be loaded and used by asterisk. More on
> this after I actually get something that appears to work -- though if
> anyone wants to comment or object, I'd appreciate hearing about it now.
=20
For applications, yes, I think perl could be a logical choice, and indeed
I had started playing with creating a perl module based on Asterisk.
The area that I feel needs the most help in terms of scripting is the
creation of extensions. The format you see in
/etc/asterisk/extensions.conf, which closely matches the internal
representation, but that ws not the (only) representation that I wanted to
provide the user. There needs to be some sort of macro language, maybe
even a scripting language.
Agreed. I'm still going to focus on application support first;
However, I may take good look thereabouts when done with that. To be
honest, I haven't yet gotten a feel for the current pbx code, and will
need to go through it quite carefully before trying to make any
changes.
Quote:
> Btw, if you offer non-anonymous CVS access (so I could just commit this
> kind of thing rather than posting it to the list), I'd be appreciative.
=20
I do have non-anonymous CVS. You can either send me patches off hte list,
or use CVS, but Unless you plan to make large changes (or large numbers of
changes), I'd rather just have you mail me patches to me personally to
apply at this point.
Okay, then -- I intend to submit the big stuff (perl support) all at
once, so this should be quite workable.
--FCuugMFkClbJLl1L
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.9 (GNU/Linux)
Comment: For info see http://www.gnupg.org
Posted: Fri Jan 07, 2000 8:32 pm Post subject: [Asterisk] A few patches, questions
On Thu, 6 Jan 2000 21:55:09 -0800, Charles C. Duffy wrote:
Quote:
Another thing -- after looking at some of the included applications, I
came to the conclusion that C is not necessarily the best language to
write them in; As a result, I'm playing with adding support for
applications written in perl to be loaded and used by asterisk. More on
this after I actually get something that appears to work -- though if
anyone wants to comment or object, I'd appreciate hearing about it now.
This is a excellent idea and should allow integration with
MisterHouse the open source home control package written in perl.
Posted: Wed Jan 12, 2000 2:25 pm Post subject: [Asterisk] A few patches, questions
Quote:
In emacs, "ispell-comments-and-strings" will do the trick.
So was that the only spelling mistake?? :)
Quote:
Agreed. I'm still going to focus on application support first;
However, I may take good look thereabouts when done with that. To be
honest, I haven't yet gotten a feel for the current pbx code, and will
need to go through it quite carefully before trying to make any
changes.
*nods* Also be sure you're using the latest CVS code.
Quote:
Okay, then -- I intend to submit the big stuff (perl support) all at
once, so this should be quite workable.
Great, and again if you need writable CVS access, we can work that out,
it's just that I prefer to review everything that goes into Asterisk to be
sure I'm never in the position of not understanding my own code (even
though that still happens sometimes ;-) )
On Wed, Jan 12, 2000 at 08:25:42AM -0600, Mark Spencer wrote:
Quote:
> In emacs, "ispell-comments-and-strings" will do the trick.
=20
So was that the only spelling mistake?? :)
Not quite (that one I caught by hand). If I do a "cvs diff" right now,
though, I'd have to go through it manually to pick the spelling fixes
out of the perl stuff, so I'll submit the rest later.
Quote:
> Agreed. I'm still going to focus on application support first;
> However, I may take good look thereabouts when done with that. To be
> honest, I haven't yet gotten a feel for the current pbx code, and will
> need to go through it quite carefully before trying to make any
> changes.
=20
*nods* Also be sure you're using the latest CVS code.
That's a bit of an issue -- I've essentually forked myself off with
this perl stuff, and can't update without potentially mucking the
stuff I've changed. What I'll probably be doing is getting perl
working with my (somewhat old) CVS snapshot, making a diff between
that and the version it's based on and then porting it up to the
current version.
Quote:
> Okay, then -- I intend to submit the big stuff (perl support) all at
> once, so this should be quite workable.
=20
Great, and again if you need writable CVS access, we can work that out,
it's just that I prefer to review everything that goes into Asterisk to be
sure I'm never in the position of not understanding my own code (even
though that still happens sometimes ;-) )
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum