Dear chicken fellows, would it be possible to categorize some of the eggs
under others, in order to present a more hierarchical and cleaner structure
of the eggs list?
For example:
> Web programming
|-- autoform
|--- autoform-jquery
|--- autoform-postgresql
|-- awful
|--
Hi everyone,
As most of you know, we had a Chicken meetup in the UK, which was great fun.
Thanks to Alaric and Sarah for their hospitality and the great food!
During this meetup I wrote a reimplementation of SCSH's UNIX process
notation macros for Chicken. This has now been released as an egg.
I
On Wed, Oct 03, 2012 at 06:21:45PM +0200, Peter Bex wrote:
> Hi all,
>
> I'm trying to figure out the behavior of process-fork and the
> handling of signal/chld (SIGCHLD). Here's a simple program
> which simply sets up a pipe and forks. The parent process reads
> from the pipe, the child writes
Hi all,
I'm trying to figure out the behavior of process-fork and the
handling of signal/chld (SIGCHLD). Here's a simple program
which simply sets up a pipe and forks. The parent process reads
from the pipe, the child writes to it.
(use posix)
#;(set-signal-handler! signal/chld void)
(receiv
Upgrade to 4.7.0.6 or 4.8.0, the fix to work with clang wasn't in until after
4.7.0. 4.6.0 is very old at this point.
Also I would build chicken with "make PLATFORM=linux C_COMPILER=clang" and then
all your eggs and code will automatically be built with clang. I doubt it is
safe to use "-cc c
Hello,
I'd like to know if it is possible to use csc with clang as a C
compiler. I started with a simple scheme "program" hello,scm
(write 42)
csc hello.scm compiled fine and really printed 42 !
csc -cc clang hello.scm
also compiled fine but the resulting executable did nothing
but to use almos
