unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Tom Lord <lord@regexps.com>
Subject: Re: new-model.text, please comment
Date: Sat, 14 Sep 2002 17:55:49 -0700 (PDT)	[thread overview]
Message-ID: <200209150055.RAA10998@morrowfield.regexps.com> (raw)
In-Reply-To: <87sn0cp4qg.fsf@zagadka.ping.de> (message from Marius Vollmer on 15 Sep 2002 00:48:39 +0200)



	> I don't think we should have the rule that the compiler can
	> assume by default that a variable will never be assigned to
	> when it is not being assigned to in the file where it is
	> defined.


Perhaps.  I dunno.  Sounds wrong to me.  But: I dunno.

Advice: pick some big app to work on.  Work on that app.  Slow down
work on the guile core -- but revise the core as your experience on
the big app accumulates.

In other words, whether or not there should be such a rule seems to me
to be the kind of question that experience can help you decide.

Write Emacs from scratch, in pure Guile, or something.

Or blow S48 out of the water as a SCSH host by writing Guile
replacements for all of the text and shell utils.

-t




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


  parent reply	other threads:[~2002-09-15  0:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 18:05 new-model.text, please comment Marius Vollmer
2002-09-12 22:48 ` Tom Lord
2002-09-14 22:48   ` Marius Vollmer
2002-09-15  0:50     ` Tom Lord
2002-09-15  0:55     ` Tom Lord [this message]
2002-09-21 20:27       ` Marius Vollmer
2002-09-12 23:28 ` Rob Browning
2002-09-13 20:22   ` Marius Vollmer
2002-09-13 20:34     ` Rob Browning
2002-09-13 18:53 ` Neil Jerram
2002-09-13 22:06   ` Rob Browning
2002-09-14  1:15     ` Lynn Winebarger
2002-09-14 22:05   ` Marius Vollmer

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=200209150055.RAA10998@morrowfield.regexps.com \
    --to=lord@regexps.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).