From: Doug Evans <xdje42@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Guile 2.0 is turning 3 years old, let's hack!
Date: Tue, 11 Feb 2014 00:10:38 -0800 [thread overview]
Message-ID: <CAP9bCMSi2J9jx-8WBtKgCVvb+khWz7YLdM9bQeGNMSihYp=PiA@mail.gmail.com> (raw)
In-Reply-To: <87mwhz1dgf.fsf@gnu.org>
On Mon, Feb 10, 2014 at 2:14 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Hello!
>
> As I'm sure you all know, Guile 2.0 was released on Feb. 16th, 2011:
>
> http://lists.gnu.org/archive/html/guile-devel/2011-02/msg00173.html
>
> This was such an important milestone for us Guilers that we've taken the
> habit to celebrate it with a friendly hackfest. The idea is to produce,
> by Feb. 16th (6 days!), the hack of your choice using Guile. It can be
> pretty much anything, as long as it's fun. :-)
>
> So in 2012 people came up with a bunch of funky projects:
>
> http://savannah.gnu.org/forum/forum.php?forum_id=7111
>
> And last year there were even more participants, and even more fun:
>
> http://savannah.gnu.org/forum/forum.php?forum_id=7509
>
> Now is the time to start up your REPL and get hacking!
>
> Ludo'.
Cool!
Can I offer something written while at FOSDEM (last week).
I used my wrap-syscall package to write a gdb bug repro that was
otherwise harder to do, and writing it *was* fun! :-)
https://github.com/xdje42/wrap-syscall
With it I can, via LD_PRELOAD, intercept system calls (or potentially
any library call) with Guile and reimplement them or just monitor
them.
Or does it have to be something written after Feb.10.
next prev parent reply other threads:[~2014-02-11 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 10:14 Guile 2.0 is turning 3 years old, let's hack! Ludovic Courtès
2014-02-10 20:21 ` Panicz Maciej Godek
2014-02-11 8:10 ` Doug Evans [this message]
2014-02-11 10:46 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2014-02-14 11:26 Nala Ginrut
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='CAP9bCMSi2J9jx-8WBtKgCVvb+khWz7YLdM9bQeGNMSihYp=PiA@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).