On 28 November 2010 05:38, Neil Jerram wrote:
> Peter Brett writes:
>
>> Sure. libgeda uses direct management of memory, and the structures used
>> in its document object model need to be explicitly deleted when finished
>> with. I decided to use a Guile smob to represent these structures for
On 28 November 2010 05:51, Neil Jerram wrote:
> Linas Vepstas writes:
>
>> Hi,
>>
>> On 25 November 2010 08:12, Andy Wingo wrote:
>>>
>>> I just hacked up a new binding to sqlite. It works with sqlite3 and
>>> Guile 1.9/2.0. Check it out at:
>>>
>>> http://gitorious.org/guile-sqlite3
>>
>> I'd
Ian Hulin writes:
> OK, here's the question: if we decide not to rely on AUTOCOMPILE, and
> we are able generate our own .go files in, say, /out/scm,
> how do we get guile to use the compiled version
> /out/scm/.go in preference to a possibly
> non-existent .scm.go file in the cache? There are
Linas Vepstas writes:
> Hi,
>
> On 25 November 2010 08:12, Andy Wingo wrote:
>>
>> I just hacked up a new binding to sqlite. It works with sqlite3 and
>> Guile 1.9/2.0. Check it out at:
>>
>> http://gitorious.org/guile-sqlite3
>
> I'd like to horn in on Andy's glory by advertising guile-dbi
>
>
Andy Wingo writes:
> Hey all,
>
> I wrote a quick binding to libexif, and threw it up on the tubes. It's
> here:
>
> http://gitorious.org/guile-exif
>
> I'm rewriting my web photo gallery from being in python to guile, hence
> the sqlite and exif hacking.
Really cool to see these quick new b
Hi Peter,
Thanks for providing such a clear explanation of the problem. Here are
a few comments.
Peter Brett writes:
> Sure. libgeda uses direct management of memory, and the structures used
> in its document object model need to be explicitly deleted when finished
> with. I decided to use a
