unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Chris Bitmead <mailinglist@bitmead.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: Thu, 04 Jul 2002 00:10:57 +1000	[thread overview]
Message-ID: <3D2305F1.2080603@bitmead.com> (raw)
In-Reply-To: 5.0.2.1.2.20020703085953.026d4b80@zima.bbn.com

> I think you'll find the performance of modern Java's, such as 1.3 or 
> 1.4 very acceptable.  When using Jscheme to do Swing GUI's you don't 
> notice any performance difference because Jscheme is just assembling 
> Swing components and Java is doing most of the work. 


I'm not worried about the gui, I'm worried about the actions of the gui. 
The app I want to do may have to do some manipulating and 
transformations of largish files.

>> call/cc, blurry picture on full tail calls etc). Kawa's type system 
>> makes it rather inconvenient to use Java libraries like Swing 
>> (strings in kawa are not strings in java etc). Neither have built in 
>> a nice CLOS-ish object system which makes life worth living.
>>
>> Let me put it this way: Is Full-Scheme-Language+CLOS+portable 
>> convenient gui on Windows+Linux too much to ask?
>
>
> SISC is a full scheme. 

Ok, I didn't know about SISC. I'm impressed that it supports full r5rs. 
I'm disappointed that the penalty of using Java and supporting tail 
calls is that the benchmarks take 2.5 times as long to run as kawa. (and 
jscheme is twice as slow again). And the option to compile Kawa to 
native and get about 10x the performance is hard to resist keeping as an 
option in reserve, as I presume you can do with Hobbit for guile. It's 
hard to throw away that option up front without knowing how much you 
will need that performance down the track.

> It shouldn't be hard to add a Scheme Swing library like Jscheme's JLIB. 

Well Jscheme supports some fancy syntax for interfacing with Java so I 
would have thought JLIB would be a bit of a job to port.

> Jscheme has chosen to stay close to Java, so integrating Scheme and 
> Java is fairly painless.  It does handle tail recursion.  

I have got a suspician it only handles "obvious" tail calls, but I'm 
happy to be proved wrong.

> While it does not have a CLOS object system, it has multimethods and 
> you can define Java classes in Scheme.
>
> To do a CLOS in a Scheme built on top of Java you need to decide how 
> the CLOS and Java objects interact.  For example, in Jython, Jython 
> classes look to Java like java classes.  However, there semantics are 
> slightly different which can get confusing.  I'll have to think about 
> how one might do CLOS in java some more. 

Well, just having CLOS would probably be ok with me, even if that aspect 
doesn't interact particularly with Java objects.

>
>
>
>> Ken Anderson wrote:
>>
>>> At 10:41 AM 7/2/2002, Chris Bitmead wrote:
>>>
>>>> Hmm, just checked out PLT-Scheme. The Gui is so limited it doesn't 
>>>> even have something like a grid or table widget. And for this app 
>>>> it's very visual I need a pretty good set of widgets, including 
>>>> some kind of grid. And the OO system looks more awful to me the 
>>>> longer I look at it, but I guess I could live with it if the gui 
>>>> was ok.
>>>>
>>>> Is there any scheme out there with some decent cross-platform gui 
>>>> support, and works on at least Windows and Unix, preferably Mac 
>>>> too? Am I asking so much?
>>>
>>>
>>> Not at all.  There are several Schemes implemented in Java that 
>>> should let you do portable gui development easily.  Here are 3:
>>>
>>> http://www.gnu.org/software/kawa/
>>> http://jscheme.sourceforge.net/jscheme/mainwebpage.html
>>> http://sisc.sourceforge.net/
>>>
>>> I use Jscheme.
>>>
>>>
>>> _______________________________________________
>>> Guile-devel mailing list
>>> Guile-devel@gnu.org
>>> http://mail.gnu.org/mailman/listinfo/guile-devel
>>
>>
>>
>>



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


  reply	other threads:[~2002-07-03 14:10 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 [this message]
2002-07-05 20:21                 ` Per Bothner
2002-07-06  2:30                   ` Chris Bitmead
2002-07-06 22:11                     ` Ken Anderson
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=3D2305F1.2080603@bitmead.com \
    --to=mailinglist@bitmead.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).