TCL was designed just for this time of application. One where you write and API in C and then use TCL script to scring the API calls togethere. Swig will build the TCL binding for you even if you choose to use only TCL.
THe choise of TCL. Perl, Java or whatever is triveal and matters little as long as the language was ODBC, networking and access to the filessystem and of corse they all have all of this. The only points that do matter are 1) Pick a language that somebody else maintains, is widely used and known and most critically has many examples of it being embeded in applactions. TCL, Perl and Guile are leaders in this area 2) Design a clean API that is language interpeter independent and you will preserve the option to switch or add another languages later with only a couple days work. 3) An RPC layer over the API could be useful. --- Justin Tunney <[EMAIL PROTECTED]> wrote: > I've talked to a few people who want to integrate Javascript, which > would > work out pretty well considering that we could, for example, hijack > Walter > Bright's (of Zortech and Symantec C++ fame) GPL implementation of > ECMAScript (http://digitalmars.com/dscript/index.html) > > However, and to be quite frank, I am shocked that no one has > suggested > using TCL. TCL is /perfect/ for OpenPBX. TCL is very lightweight, > uses > BSD-style license, and is ghoulishly easy to embed in to C > applications. > TCL is also easy to learn and has years of experience under its belt > for > embedding in C applications. Furthermore, there is a SourceForge > project > for TCL ODBC support (http://sf.net/projects/tclodbc/). I am not > sure > what the status of this project is because SF is down right now. > > Here's a tutorial on how to embed TCL in your C application: > http://wiki.tcl.tk/2074 > > TCL would certainly save all the OpenPBX developers a _lot_ of time > implementing GOOD dialplan scripting. After all, the common > consensus > here is to reinvent as few wheels as possible, TCL will let us do > that > better than any other language. (As opposed to AEL which is too good > to > even use flex/bison) > > -Justin Tunney > > On Thu, 08 Dec 2005 22:41:59 -0500, Daniel Swarbrick > <[EMAIL PROTECTED]> wrote: > > > Hi everybody, > > > > Has there been any more progress made on the decision to replace > > pbx_config with an alternative dialplan language? The last murmurs > I > > heard were that it would possibly be Javascript. I realise that we > have > > res_js integrated, but it's still essentially just a translator > like > > AEL, to the core pbx_config methods. > > > > When can we break away from the clunky nature of extension > priorities, > > and have a dialplan flow more like a typical procedural language > such as > > Javascript, PHP or Python, with real functions? > > > > If we can come to a reasonable consensus about what the next step > > forward is, I'm keen to spend a bit of time investigating the > > feasibility of rewriting some of the apps like app_voicemail in the > new > > scripted dialplan language (ie Javascript perhaps). > > > > Also, is this kind of thing going to be affected by the ICD stuff? > > > > Cheers, > > Daniel "pressureman" Swarbrick > > _______________________________________________ > > Openpbx-dev mailing list > > [email protected] > > http://lists.openpbx.org/mailman/listinfo/openpbx-dev > > _______________________________________________ > Openpbx-dev mailing list > [email protected] > http://lists.openpbx.org/mailman/listinfo/openpbx-dev > Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Cell: 310-990-7550 Office: 310-336-5189 [EMAIL PROTECTED] KG6OMK __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
