On Mon, Apr 29, 2019 at 11:12:07AM +0100, Brandon Invergo wrote:
> Hi,
>
> Thanks for your response.
>
> to...@tuxteam.de writes:
>
> > Quoth the docs
> >
> > " -- generic: deep-clone
> > -- method: deep-clone (self )
> > Return a “deep” clone of SELF. The default method makes a deep
> >
And since I apparently can't use git properly, here is the
patch for guile2-xlib.pc.in.
--
hugo
>From 33bcb624e00672fb71416727cb8c49ac80945ef6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Hugo=20H=C3=B6rnquist?=
Date: Mon, 29 Apr 2019 13:01:45 +0200
Subject: [PATCH] Add pc.in file.
---
guile2-xlib.
Hello!
I have patches for both guile2-xlib [1] and guile-cairo [2].
This adds xlib bindings to cairo, allowing output to a
screen. To archive this I had to patch guile2-xlib to work
as a library. Attached is a number of patches to the first,
and one big patch to the later. Along with cairo's
"offi
Hi,
Thanks for your response.
to...@tuxteam.de writes:
> Quoth the docs
>
> " -- generic: deep-clone
> -- method: deep-clone (self )
> Return a “deep” clone of SELF. The default method makes a deep
> clone by allocating a new instance and copying or cloning slot
> values from s
On Mon, Apr 29, 2019 at 09:44:09AM +0100, Brandon Invergo wrote:
> Hello,
>
> I don't understand the following behavior:
>
> scheme@(guile-user)> (use-modules (oop goops))
> scheme@(guile-user)> (define-class () (gob #:accessor gob
> #:init-keyword #:gob))
> scheme@(guile-user)> (define a (make
Hello,
I don't understand the following behavior:
scheme@(guile-user)> (use-modules (oop goops))
scheme@(guile-user)> (define-class () (gob #:accessor gob
#:init-keyword #:gob))
scheme@(guile-user)> (define a (make #:gob '(foo)))
scheme@(guile-user)> (define b (deep-clone a))
scheme@(guile-use
