unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Tom Lord <lord@regexps.com>
Cc: rlb@defaultvalue.org, mvo@zagadka.ping.de, guile-devel@gnu.org
Subject: Re: Recursive mutexes?
Date: Sun, 27 Oct 2002 09:21:49 -0800 (PST)	[thread overview]
Message-ID: <200210271721.JAA29475@morrowfield.regexps.com> (raw)
In-Reply-To: <m34rb8ffgz.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 27 Oct 2002 08:33:48 +0000)



	Tom> Java semantics seem to me much, much nicer for MIMD (just intuitively,
	Tom> no elaborate argument).   

	What are MIMD and SISD?

"multiple/single instruction; multiple/single data" -- i.e. ordinary
multi- and single CPU systems.   (I'm not sure anyone really bothers
to say SISD -- I made it up.   People do say SIMD.)

	I like Java's synchronized/notify/wait model very much, but
	how would you express it in Scheme without adding lots of
	Java-ish class declaration stuff?  

The suggestion is that you _do_ look into combining the languages.

One way to do it is kawa-style in which (caution: this is from old
memory) every scheme value is a java object and vice versa.  That
isn't what I was suggesting.

I was suggesting something more layered: Another way to do it is to
have a universe of java-ish objects, shared between threads, and one
store of Scheme objects per thread.  Fine-grain multi-threaded parts
in java-ish; course-grain in Scheme, coordinating via call-outs to
java-ish.  If Guile is currently layered "Scheme over C", this would
make it layered "Scheme over both C and java-ish-over-C".

If Emacs were done that way, for example, you might wind up with
low-level buffers and redisplay in java-ish (redisplay in its own
thread); and scheme-extensible threads for handling user interaction,
subprocess mgt, redisplay customization, etc.

Part of the idea here was to be able to leverage other people's
java-ish implementation work in an easy (heh) way.

Even though it's not a Schemishly minimalist approach, I think this
might actually be a nice model to use when building programs (as in,
"easy to write good, correct, maintainable programs with").


	How would it map onto GOOPS?

Doesn't goops have enough of a MOP to support optimized
representations given restrictions on the optimized types?

-t


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


  reply	other threads:[~2002-10-27 17:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 20:35 Recursive mutexes? Marius Vollmer
2002-10-26 21:39 ` Neil Jerram
2002-10-27  0:03   ` Marius Vollmer
2002-10-27  1:20     ` Thomas Bushnell, BSG
2002-10-27 12:36       ` Marius Vollmer
2002-10-27  7:55     ` Neil Jerram
2002-10-27 18:33       ` Rob Browning
2002-10-26 22:16 ` Rob Browning
2002-10-26 22:29   ` Rob Browning
2002-10-26 22:42   ` Tom Lord
2002-10-26 23:26     ` Thomas Bushnell, BSG
2002-10-26 23:35       ` Tom Lord
2002-10-26 23:50         ` Tom Lord
2002-10-27  1:18           ` Thomas Bushnell, BSG
2002-10-26 22:47   ` Tom Lord
2002-10-27  8:33     ` Neil Jerram
2002-10-27 17:21       ` Tom Lord [this message]
2002-10-27  0:35   ` Marius Vollmer
2002-10-27  4:36     ` Rob Browning
2002-10-27 11:32       ` Marius Vollmer
2002-10-27 18:44         ` 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=200210271721.JAA29475@morrowfield.regexps.com \
    --to=lord@regexps.com \
    --cc=guile-devel@gnu.org \
    --cc=mvo@zagadka.ping.de \
    --cc=rlb@defaultvalue.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).