From: maledetto <maledetto@online.de>
To: guile-user@gnu.org
Subject: Re: a straight way to testing the own scheme capabilities?
Date: Thu, 20 Jan 2011 23:12:25 +0100 [thread overview]
Message-ID: <20110120231225.3974a2e4.maledetto@online.de> (raw)
In-Reply-To: <87ei87v70a.fsf@ambire.localdomain>
On Thu, 20 Jan 2011 18:07:17 +0100
Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () maledetto <maledetto@online.de>
> () Thu, 20 Jan 2011 17:48:40 +0100
>
> my simple intention is to do a straight check how 'fit' i am in
> scheme without studying multiple thick books and their examples. do
> you have any good hints?
>
> You can pick some Scheme code out there and read it, with an eye
> on adding comments and posting the diffs to be incorporated upstream.
> This exercise will help you gauge your understanding against that of
> those who maintain the code. Some positive side effects: code review,
> more comments (at an "appropriate" level), interaction with multiple
> "real world" examples and people. Caveat: the latter might degenerate
> into a negative experience, people being what they are, but then
> that's life outside the books.
>
many thanks for the comments. but they rather target at programming
skills and not that at knowledge-about-the-language (call/cc, ,@,
etc.) they also aint the quickest ways ;) aren't there some tests out
there?
regards,
maledetto <maledetto@online.de>
next prev parent reply other threads:[~2011-01-20 22:12 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 [this message]
2011-01-21 10:21 ` Thien-Thi Nguyen
2011-01-21 14:07 ` Joel James Adamson
2011-01-21 17:18 ` maledetto
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=20110120231225.3974a2e4.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).