From: Linas Vepstas <linasvepstas@gmail.com>
To: Daniel Kraft <d@domob.eu>
Cc: guile-user@gnu.org, richard.shann@virgin.net
Subject: Re: calling scheme procedures by name from C
Date: Sun, 2 Aug 2009 14:15:49 -0500 [thread overview]
Message-ID: <3ae3aa420908021215k106da181w6f3c1292718c8f99@mail.gmail.com> (raw)
In-Reply-To: <4A75D612.7010801@domob.eu>
2009/8/2 Daniel Kraft <d@domob.eu>:
> Linas Vepstas wrote:
>>
>> 2009/8/2 Mike Gran <spk121@yahoo.com>:
>>>
>>> Oh my oh my. I wrote that doc at lonelycactus.com quite awhile ago. I
>>> keep meaning to take it down, because the way I did things was a little
>>> strange and a little old. But, oddly, there are few other
>>> tutorial-level resources. Someone really ought to put something better
>>> together.
>>
>> Well, don't take it down; it doesn't use the gh_ functions from what
>> I can tell, so its not totally misleading. I'm more concerned about
>> the 'turtle graphics' pages, which do use the gh_* functions. What
>> I do like about that one is that its fairly short and concise, which is
>> what I tend to like best.
>
> I also got started using Guile with that turtle package tutorial, and it was
> really quite nice for the purpose... But I also later rewrote my original
> code to not use gh_ after I discovered there was a new API ;)
>
> This document is linked here:
> http://www.gnu.org/software/guile/docs/guile-tut/tutorial.html
>
> So it seems to be part of the "official documentation" somewhat...
Well, its on the main gnu.org website, so it doesn't get much
more official than that.
> However,
> it does not seem to be the stuff in doc/tutorial (actually, grepping doc for
> tortoise does not give any hits at all?)
?? It is linked directly from the main guile documentation page at
http://www.gnu.org/software/guile/docs/
which is linked directly from the main guile page at:
http://www.gnu.org/software/guile/
> -- so does anyone know who wrote it
> and where/what it is meant to be?
I don't get what you are saying ...
at the bottom of your URL it says clearly:
"I wrote this page because ... etc
Copyright (c) 2000 David Drysdale
Permission is granted to copy, distribute and/or modify ...
GNU Free Documentation License,
> If that's no problem with the original author, I'd volunteer to rework the
> tutorial for the new Guile API.
Well, with the GFDL, you don't have to contact the original author.
You can hack away at it as desired.
> Or maybe write some other tutorial in the
> same style just with another example (that maybe does not use X functions
> but something more basic).
Yeah, X examples are rather anachronistic. I dunno, an OpenGL
version might be fun. Imagine .. 3D programming in scheme ..!
it would not be a bad idea, I don't think.
Anyway, doing something interactive would be appropriate --
something vaguely enjoyable when its done. Maybe a simple
fractal explorer?
> What do you think about this?
Do it!
--linas
next prev parent reply other threads:[~2009-08-02 19:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 9:17 calling scheme procedures by name from C Richard Shann
2009-08-02 11:17 ` Linas Vepstas
2009-08-02 12:03 ` Richard Shann
2009-08-02 15:00 ` Mike Gran
2009-08-02 17:22 ` Linas Vepstas
2009-08-02 18:08 ` Daniel Kraft
2009-08-02 19:15 ` Linas Vepstas [this message]
2009-08-02 19:37 ` Daniel Kraft
2009-08-02 20:07 ` Linas Vepstas
2009-08-13 23:19 ` Updated Guile Tutorial Neil Jerram
2009-08-02 13:00 ` calling scheme procedures by name from C Paul Emsley
2009-08-02 13:35 ` Richard Shann
2009-08-02 19:51 ` Peter TB Brett
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=3ae3aa420908021215k106da181w6f3c1292718c8f99@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=d@domob.eu \
--cc=guile-user@gnu.org \
--cc=richard.shann@virgin.net \
/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).