Acquisition of LispWorks and Liquid Common Lisp
Unable to parse email body. Email id is 3334
Unable to parse email body. Email id is 3334
Unable to parse email body. Email id is 3335
Unable to parse email body. Email id is 3346
Marco Antoniotti <marcoxa@cs.nyu.edu> writes: > On Jan 4, 2005, at 12:26 PM, davef@lispworks.com wrote: >> >> We do offer discounts to academic institutions, and also an academic >> site license (pricing at www.lispworks.com/buy). > > I do not know about Franz's offering, but I think you should revise > you offer for the "academic site" license. While very attractive, it > lacks the SQL module. I don't thinkg that really is aproblem cl-sql works fine with LispWorks... Regards Friedrich
On Wed, 05 Jan 2005 10:02:45 +0100, Friedrich Dominicus <frido@q-software-solutions.de> wrote: > Marco Antoniotti <marcoxa@cs.nyu.edu> writes: > >> I do not know about Franz's offering, but I think you should revise >> you offer for the "academic site" license. While very attractive, >> it lacks the SQL module. > I don't thinkg that really is aproblem cl-sql works fine with > LispWorks... The main difference probably is that CommonSQL is supported by LispWorks Ltd. while CL-SQL isn't. Anyway, here's a technical question: CL-SQL uses the FFI (except for the PostgreSQL socket interface) and thus one lengthy database operation has the potential to block all other threads on platforms with non-native threads, i.e. everywhere except on Windows. Will that be the same with CommonSQL or do they differ? Thanks, Edi.