Re: Perl API

2000-11-02 Thread Darren/Torin/Who Ever...
Rob Browning, in an immanent manifestation of deity, wrote: If SWIG does a good job, then yes, but if it's not going to provide a good solution, then I'd rather just see each interested group create and maintain bindings for that language until/if/unless there's a unified solution that actually

Re: Perl API

2000-11-01 Thread Darren/Torin/Who Ever...
Rob Browning, in an immanent manifestation of deity, wrote: On Wed, 01 Nov 2000 16:20:05 Clinton Popetz wrote: | One key advantage of doing it in SWIG is that SWIG can spew out Python | interfaces as well, and I hear there are people who actually like | programming in Python. shudder :)

Re: Perl API

2000-11-01 Thread Rob Browning
"Darren/Torin/Who Ever..." [EMAIL PROTECTED] writes: Okay. I'll look for this. If we're going to have to update a major portion of the Perl API, we might want to just use XS. This would free us from the dependency on swig. I have a lot more experience with XS as well. :) Hmm.

Re: Perl API

2000-11-01 Thread D-Man
On Wed, 01 Nov 2000 16:20:05 Clinton Popetz wrote: | One key advantage of doing it in SWIG is that SWIG can spew out Python | interfaces as well, and I hear there are people who actually like | programming in Python. shudder :) | Python is much nicer than perl anyways. ;-) I like it a

Re: Perl API

2000-11-01 Thread Clinton Popetz
On Wed, Nov 01, 2000 at 02:34:00PM -0600, Rob Browning wrote: "Darren/Torin/Who Ever..." [EMAIL PROTECTED] writes: Okay. I'll look for this. If we're going to have to update a major portion of the Perl API, we might want to just use XS. This would free us from the dependen

Re: Perl API

2000-11-01 Thread Rob Browning
"Darren/Torin/Who Ever..." [EMAIL PROTECTED] writes: I suspect that having easy bindings for Perl, Python, Tcl/Tk, and Ruby pretty much says that we'll use SWIG. If SWIG does a good job, then yes, but if it's not going to provide a good solution, then I'd rather just see each interested group

Re: Perl API

2000-10-31 Thread Darren/Torin/Who Ever...
of time, btw, as the API will have changed quite a bit. Okay. I'll look for this. If we're going to have to update a major portion of the Perl API, we might want to just use XS. This would free us from the dependency on swig. I have a lot more experience with XS as well. :) It might be useful

Re: Perl API

2000-10-30 Thread Darren/Torin/Who Ever...
Dave Peticolas, in an immanent manifestation of deity, wrote: Who uses the Perl API? I do. But I suspect that I'm one of the few. I just don't have the time to (re-)learn scheme. I used lisp in the 80s but these days, I only use it for (X)Emacs. The reason I ask is that the Perl API

Re: Perl API

2000-10-30 Thread Dave Peticolas
"Darren/Torin/Who Ever..." writes: Dave Peticolas, in an immanent manifestation of deity, wrote: Who uses the Perl API? I do. But I suspect that I'm one of the few. I just don't have the time to (re-)learn scheme. I used lisp in the 80s but these days, I only use it fo

Perl API

2000-10-24 Thread Dave Peticolas
Who uses the Perl API? The reason I ask is that the Perl API is rapidly becoming out-of-date as the engine is extended and the swig interface is not kept up to date. Given the difficulties of using swig, we'd like to drop it. Is there any interest in keeping the Perl API? Is anyone interested