[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: using gprolog to make a shared library
From: |
Taco Witte |
Subject: |
Re: using gprolog to make a shared library |
Date: |
Thu, 3 Jan 2013 17:51:41 +0100 |
Hi Daniel,
Thanks for your answer. Using a socket certainly works (that's what I
have now). It's a bit fragile though and slow to start.
Is there something I can help with to get support for shared libraries closer?
Kind regards,
Taco
On Thu, Jan 3, 2013 at 10:47 AM, Daniel Diaz <address@hidden> wrote:
> Hi Taco,
>
> sorry there is no news on this point… gprolog cannot create shared libs. Even
> if less easy to use you can try to have 2 separate processes (your gprolog
> program and your ruby program) and establish a connection via a socket (I
> know several projects doing this).
>
> Anyway, this is an important missing feature: we have to add it (technically
> this is not a problem but we have to modify all existing ports to provide
> this...).
>
> Daniel
>
>
> Le 2 janv. 2013 à 13:51, Taco Witte <address@hidden> a écrit :
>
>> Hi,
>>
>> In order to interface with GNU Prolog I'd like to implement a C
>> interface and compile that into a shared library with gprolog. Next I
>> plan to use the shared library from Ruby with its support for calling
>> native code.
>>
>> This wasn't possible in 2003, I see [1]. Does anybody perhaps know
>> whether it's supported now? Thank you!
>>
>> Kind regards,
>> Taco Witte
>>
>> [1] http://lists.gnu.org/archive/html/bug-prolog/2003-06/msg00003.html
>>
>> _______________________________________________
>> Users-prolog mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/users-prolog
>>
>> --
>> Ce message a ete verifie par MailScanner
>> pour des virus ou des polluriels et rien de
>> suspect n'a ete trouve.
>>
>
>
> --
> Ce message a ete verifie par MailScanner
> pour des virus ou des polluriels et rien de
> suspect n'a ete trouve.
>