From: Christopher Cramer <crayc@pyro.net>
Cc: guile-devel@gnu.org
Subject: Re: Roadmap and goals?
Date: Wed, 17 Apr 2002 19:57:03 -0500 [thread overview]
Message-ID: <20020417195703.B12649@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <3CBD68DB.2CC96A4F@staff.ttu.ee>; from tammet@staff.ttu.ee on Wed, Apr 17, 2002 at 03:21:47PM +0300
On Wed, Apr 17, 2002 at 03:21:47PM +0300, Tanel Tammet wrote:
> To do that, I'd have to understand where is
> the Guile development moving, what are the prioritized
> goals, crucial principles, etc. What would be
> the projects inside Guile where a person
> like me could possibly help.
There's some stuff in CVS discussing this, e.g.:
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile/workbook/policy/plans.text?rev=1.1&content-type=text/vnd.viewcvs-markup
http://savannah.gnu.org/cgi-bin/viewcvs/guile/guile/workbook/tasks/TODO?rev=1.33&content-type=text/vnd.viewcvs-markup
> For example, why exactly should somebody
> use Guile instead of SCM or Bigloo:
> what are the specific advantages and
> what is the downside. Why not use just
> SCM or Bigloo (they are faster, you know :-)
> There have to be answers to this question,
> just that I do not know the answers.
I haven't checked out SCM in a long time, so there is a slight possibility
this isn't true anymore, but the advantage Guile has over SCM is that
integration with C is much easier. There was some reason why I decided
to use Guile instead of Bigloo, but I really can't remember what it
was anymore. I know SCM is a little faster than Guile, but I was not
under the impression that Bigloo was.
--
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
Quoi que vous fassiez, écrasez l'infâme, et aimez qui vous aime.
-- Voltaire
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-18 0:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 12:21 Roadmap and goals? Tanel Tammet
2002-04-17 20:59 ` Neil Jerram
2002-04-18 8:37 ` Panagiotis Vossos
2002-04-19 9:14 ` Panagiotis Vossos
2002-04-20 6:58 ` Thien-Thi Nguyen
2002-04-20 10:18 ` Panagiotis Vossos
2002-04-18 14:58 ` bitwize
2002-04-18 19:26 ` Rob Browning
2002-04-20 7:23 ` Thien-Thi Nguyen
2002-04-18 0:57 ` Christopher Cramer [this message]
2002-04-19 17:36 ` Marius Vollmer
2002-04-19 8:38 ` Nicolas Neuss
2002-04-21 15:14 ` Rob Browning
2002-04-21 22:26 ` bitwize
2002-04-22 18:36 ` Kirill Lisovsky
2002-04-23 7:53 ` rm
2002-04-23 15:11 ` Rob Browning
2002-04-20 7:47 ` Thien-Thi Nguyen
2002-05-14 8:26 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 12:55 Kirill Lisovsky
2002-04-20 20:01 ` Rob Browning
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=20020417195703.B12649@kiwi.pyrotechnics.com \
--to=crayc@pyro.net \
--cc=guile-devel@gnu.org \
/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).