unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Ken Anderson <kanderson@bbn.com>
Cc: guile-devel@gnu.org, guile-user@gnu.org,
	Timothy Hickey <timhickey@mac.com>
Subject: Re: Guile and MS-Windows on Major Govt. Project...
Date: Sat, 06 Jul 2002 18:11:46 -0400	[thread overview]
Message-ID: <agc3p6$9ic$2@main.gmane.org> (raw)
In-Reply-To: <3D265661.9030201@bitmead.com>

At 10:30 PM 7/5/2002, Chris Bitmead wrote:


>>>Yeah, ok well they should be considered. But jscheme is an interpreter 
>>>within an interpreter == unnecessarily slow. None of them technically 
>>>are Scheme (no call/cc, blurry picture on full tail calls etc).
>>
>>
>>I'm curious what you actually want to have full call/cc for - except as a 
>>"check-off (completeness) item.
>
>
>As far as I know, I don't. Does anyone know prior to starting a project if 
>it is needed? Also, what if I pull in an external library that uses it? 
>Ok, I'm not quite experienced enough in Scheme to know how likely that is.


I'm a beginner too, having only done Scheme for the past 4.5 years.  To 
make it worse, my scheme never had call/cc, so i never learned how to take 
advantage of it. My current belief is that if your Scheme has full call/cc, 
you just use it.  If it doesn't, you make do without it, because that's 
what you do in any language that's missing the feature you want.

Dick Gabriel made a comment about Scheme once, that suggested to me that 
without call/cc Scheme is relatively easy to implement in languages like C 
and Java.  Requiring call/cc is an extra step in language 
implementation.  Probably a step as least as large as requiring 
GC.  Perhaps we are currently more willing to live without call/cc than we 
are about living without GC.

We need to provide good examples of using call/cc, so that future 
implementations will be more willing to provide it.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-07-06 22:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27 14:14 Guile and MS-Windows on Major Govt. Project Chris Bitmead
2002-06-28  1:49 ` Bruce Korb
2002-06-28  5:51   ` Chris Bitmead
     [not found]     ` <20020628210155.C3696@kiwi.pyrotechnics.com>
2002-06-29  3:32       ` Guile and MS-Windows / GTK+ Chris Bitmead
2002-07-09 21:17         ` Neil Jerram
2002-07-10  0:40           ` Chris Bitmead
2002-07-01  3:46     ` Guile and MS-Windows on Major Govt. Project Clinton Ebadi
2002-07-01 23:09       ` Chris Bitmead
2002-07-02  1:13         ` Clinton Ebadi
     [not found]         ` <200207012113.58958.unknown_lamer@unknownlamer.org>
2002-07-02 14:41           ` Chris Bitmead
2002-07-02 15:29             ` Ken Anderson
2002-07-03 12:47               ` Chris Bitmead
2002-07-03 13:27                 ` Ken Anderson
2002-07-03 14:10                   ` Chris Bitmead
2002-07-05 20:21                 ` Per Bothner
2002-07-06  2:30                   ` Chris Bitmead
2002-07-06 22:11                     ` Ken Anderson [this message]
2002-07-07 15:35                     ` Per Bothner

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='agc3p6$9ic$2@main.gmane.org' \
    --to=kanderson@bbn.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=timhickey@mac.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).