Licensing shouldn't be an issue. I have permission from the university to
release it into "the public domain." However, I intend to attach the BSD
style license/disclaimer which exists with PostgreSQL. Matlab's license
does not impose any restrictions on programs written using their API.
However, to compile the routines, one would need Matlab installed in order
to pick up some of their header files.
Darrin Rothe
rothe@asu.edu
> -----Original Message-----
> From: The Hermit Hacker [mailto:scrappy@hub.org]
> Sent: Friday, October 13, 2000 8:58 PM
> To: Darrin Rothe
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Matlab Mex Interface
>
>
> On Fri, 13 Oct 2000, Darrin Rothe wrote:
>
> > We have recently developed an interface to PostgreSQL for Matlab.
> >
> > The interface is implemented as 'C' mex wrappers around libpq.
> Most of the
> > database connection and query execution functions are
> implemented, and it
> > supports default (text) and binary transfers directly into
> Matlab variables
> > (including text, integer, and floating point arrays).
> >
> > The functions have been tested on Linux, SGI 32 bit, and Windows
> > architectures. Other architectures should be trivial to
> support - just a
> > matter of compiling.
> >
> > We would like to make this interface freely available, and would like to
> > know how much interest there would be in the interface. Also,
> would it be
> > worthwhile to package and make available with PostgreSQL.
>
> the only problem that I could see with this is the license that it is
> under ... if under BSD license, we could easily extend configure to have a
> --with-matlab option ...
>
>
>