From: Daniel Kraft <d@domob.eu>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>, Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Updated Guile Tutorial
Date: Tue, 07 Sep 2010 15:17:54 +0200 [thread overview]
Message-ID: <4C863B82.4010409@domob.eu> (raw)
I forgot to CC, so here again.
-------- Original Message --------
Subject: Re: Updated Guile Tutorial
Date: Tue, 07 Sep 2010 15:15:34 +0200
From: Daniel Kraft <d@domob.eu>
To: Andy Wingo <wingo@pobox.com>
References: <4A7B223E.6050501@domob.eu> <m3ljlollb7.fsf@pobox.com>
<4A92B446.2090902@domob.eu> <87tyyxsheh.fsf@ossau.uklinux.net>
<m3tymrtazy.fsf@unquote.localdomain> <4C6FE4E8.6030201@domob.eu>
<m3pqx2378m.fsf@unquote.localdomain>
Andy Wingo wrote:
>> from my point of view, I'd be glad if you replaced the old tutorial with
>> my version
>
> I have done so on the web site, thanks.
Cool!
>
>> (and included it into the source distro / manual -- feel free
>> to do the copyright assignment and licensing as required for that).
>
> I'm happy to do that, but it would be some work -- both documents have
> fine tone, but they are not the same tone ;)
Yes, maybe it's best to not introduce the tutorial as an "integral part"
of the manual -- but rather as a seperate item, which may be referred to
or linked to in the manual. what do you think?
> Also because there's no gnuplot library, it's hard to cover the spectrum
> of "extending applications in Guile".
>
> On the other hand, there is GNU plotutils, which does have a library:
>
> http://www.gnu.org/software/plotutils/
>
> But on the other other hand, it seems quite bitrotten...
I also have this impression, unfortunately. But if you see a "good" way
to do the visualization instead of forking gnuplot, I'm happy to adapt
the tutorial.
>> What's the dynamic FFI? I notice that I unfortunately lost contact to
>> Guile some time ago (over the last year at university that was very
>> work-intensive).
>
> See
> http://www.gnu.org/software/guile/docs/master/guile.html/Dynamic-FFI.html#Dynamic-FFI.
Well, *that* looks really cool! I have to give it a try soon :D Do you
have a suggestion for how to integrate this with the manual? It seems
to me that with such a small project it does not make sense to do both
registering procedures from C and using the FFI. But maybe we could
just call some libc function at one place? Although I have no idea so far.
Yours,
Daniel
--
http://www.pro-vegan.info/
--
Done: Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
--
http://www.pro-vegan.info/
--
Done: Arc-Bar-Cav-Kni-Ran-Rog-Sam-Tou-Val-Wiz
To go: Hea-Mon-Pri
next reply other threads:[~2010-09-07 13:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 13:17 Daniel Kraft [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 18:34 Updated Guile Tutorial Daniel Kraft
2009-08-12 22:27 ` Andy Wingo
2009-08-13 7:43 ` Daniel Kraft
2009-08-24 15:39 ` Daniel Kraft
2009-09-20 16:35 ` Neil Jerram
2009-09-20 20:31 ` Daniel Kraft
2010-08-19 5:41 ` Andy Wingo
2010-08-21 14:38 ` Daniel Kraft
2010-08-28 18:46 ` Andy Wingo
2009-09-20 16:42 ` Neil Jerram
2009-09-20 17:17 ` Chris Bryant
2009-09-20 21:13 ` Neil Jerram
2009-09-20 17:18 ` Chris Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C863B82.4010409@domob.eu \
--to=d@domob.eu \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).