Hello, all--
I have a question that is not Chicken-specific, or even scheme-specific,
but since it relates to a project I'm developing in Chicken Scheme, I hope
you will humor me.
I have been working on a framework for interactive command-line programs. I
have an initial version that works for my
On Mon, Sep 3, 2012 at 11:29 AM, Mario Domenech Goulart <
mario.goul...@gmail.com> wrote:
>
> Very nice. Thanks for making your code available.
>
You're welcome.
> I noticed that the egg documentation doesn't contain a link to the
> sources location. Usually egg authors add something like a "
Hi Matt,
On Mon, 3 Sep 2012 11:20:15 -0600 Matt Gushee wrote:
> Well, here's my first egg. It wasn't going to be: I am developing an
> egg that provides a framework for interactive command-line
> programs. But I realized in order to test that egg, I'd need a way to
> simulate user input. Hence .
On Mon, Sep 03, 2012 at 11:20:15AM -0600, Matt Gushee wrote:
> Hello, all--
Hi Matt!
> Well, here's my first egg. It wasn't going to be: I am developing an egg
> that provides a framework for interactive command-line programs. But I
> realized in order to test that egg, I'd need a way to simulate
Hello, all--
Well, here's my first egg. It wasn't going to be: I am developing an egg
that provides a framework for interactive command-line programs. But I
realized in order to test that egg, I'd need a way to simulate user input.
Hence ... dummy-user!
The egg is BSD-licensed, and should be quit
Hello Chicken users,
Recently a vulnerability was found in some of Chicken's string processing
code. As you know, NUL bytes are representable by Scheme strings, but
not by C strings (where they are treated as terminators). This mismatch
is properly handled by the FFI by throwing an exception whe
