From: maledetto <maledetto@online.de>
To: guile-user@gnu.org
Subject: Re: a straight way to testing the own scheme capabilities?
Date: Fri, 21 Jan 2011 18:18:42 +0100 [thread overview]
Message-ID: <20110121181842.bfa69ce2.maledetto@online.de> (raw)
In-Reply-To: <m3hbd2bb9m.fsf@chondestes.bio.unc.edu>
On Fri, 21 Jan 2011 09:07:49 -0500
Joel James Adamson <adamsonj@email.unc.edu> wrote:
> Thien-Thi Nguyen <ttn@gnuvola.org> writes:
>
> > () maledetto <maledetto@online.de>
> > () Thu, 20 Jan 2011 23:12:25 +0100
> >
> > aren't there some tests out there?
> >
> > What would such a test look like?
>
> To the OP: Can you be more specific about what you want? I suggest
> reading The Little Schemer[1] if you want to really understand the
> concepts behind the language. That book advanced my thinking
> hugely. I still refer to it occasionally.
>
> Joel
>
there's a simple reason for my question. i'm in the need to quickly
refresh my knowledge about the language because of a possible job in the
very near future. reading full books is a bit overhead in that short
time, and i tend to always find everything plausible in books without
being able to reproduce what i read. i rather like tutorials and
stuff that stays with the detail. but what i really want to reach is a
safe feeling. i just want to get sure about the current state of my
own, rusty knowledge about scheme. this is why i rather liked to 'test'
myself (like in school, but no multiple choice ;) the quick, easy and
dirty way.
regards,
maledetto <maledetto@online.de>
next prev parent reply other threads:[~2011-01-21 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 16:48 a straight way to testing the own scheme capabilities? maledetto
2011-01-20 16:58 ` Aleix Conchillo Flaqué
2011-01-20 17:07 ` Thien-Thi Nguyen
2011-01-20 22:12 ` maledetto
2011-01-21 10:21 ` Thien-Thi Nguyen
2011-01-21 14:07 ` Joel James Adamson
2011-01-21 17:18 ` maledetto [this message]
2011-01-21 18:42 ` Joel James Adamson
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=20110121181842.bfa69ce2.maledetto@online.de \
--to=maledetto@online.de \
--cc=guile-user@gnu.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).