unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Maciek Godek" <pstrychuj@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Me no understand scoping
Date: Sat, 2 Aug 2008 18:43:37 +0100	[thread overview]
Message-ID: <49dd78620808021043h66f6d953uff37c35d018afb80@mail.gmail.com> (raw)
In-Reply-To: <e2ceda030807311607o61c8ccc3w59a265da12f5206a@mail.gmail.com>

2008/8/1 Maciek Godek <pstrychuj@gmail.com>:
>
> I can't tell you precisely (because I don't know myself).
> It's just that whenever I try to do something in scheme,
> I end up with questions of that sort. (Maybe the thing is
> that I try to write as little code as possible -- the prettiness
> and simplicity of scheme convinces me to do so).
>
> I'm currently working on a little project (in my spare time). [...]

Many thanks for providing this description.  The project looks fun, so
I hope it continues to go well.

A few thoughts occurred to me when reading through.

1. IMO this could be really beautifully done in GOOPS, by defining
custom metaclasses and slot types.

2. You say that your protocol is lisp-ish.  I have found it really
useful, both in GDS and in another client/server project, to express
the protocol entirely in lisp forms.  Simply because this means that
you can use `read' to read exactly one protocol instruction; no
parsing required!

3. It's still not obvious to me how this ends up using the-environment
and local-eval.  If class variables never interact directly with the
real environment, they could be just stored in a hash table..

> PS gdm rocks! (thankyouthankyouthankyou!! it really did change
> my way of writing the code)

Do you mean GDS?  If so, thanks for your thanks!

Regards,
         Neil




  reply	other threads:[~2008-08-02 17:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29 21:18 Me no understand scoping Maciek Godek
2008-07-30  3:24 ` Clinton Ebadi
2008-07-30  8:42   ` Maciek Godek
2008-07-30 14:03     ` Jon Wilson
2008-07-30 15:04       ` Klaus Schilling
2008-07-30 19:24       ` Maciek Godek
2008-07-31  7:20         ` Neil Jerram
2008-07-31 19:21           ` Maciek Godek
2008-07-31 21:37             ` Neil Jerram
2008-07-31 23:07               ` Maciek Godek
2008-08-02 17:43                 ` Neil Jerram [this message]
2008-08-02 21:36                   ` Maciek Godek
2008-08-08 20:54                     ` Neil Jerram
2008-08-10 21:49                       ` Maciek Godek
2008-08-09 11:05                     ` Andy Wingo
2008-08-10 22:30                       ` Maciek Godek
2008-09-11 14:56                       ` JonWilson
2008-07-31 23:48             ` Clinton Ebadi
2008-08-01 22:00               ` Maciek Godek
2008-08-02  5:13                 ` Jon Wilson
2008-08-02 21:35                   ` Maciek Godek
     [not found] <cmu-lmtpd-29005-1217434291-0@mail-imap1.uio.no>
2008-07-30 16:18 ` Kjetil S. Matheussen
2008-07-30 19:03   ` Clinton Ebadi

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=49dd78620808021043h66f6d953uff37c35d018afb80@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-user@gnu.org \
    --cc=pstrychuj@gmail.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).