Hi!
Graham Fawcett has submitted the 256th egg:
http://chicken.wiki.br/sqlora
Thanks, Graham!
cheers,
felix
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
On 1/9/07, Daniel Sadilek <[EMAIL PROTECTED]> wrote:
Hello,
Hallo, Daniel.
I am wondering what is the best way to structure a project in Chicken.
I found no contiguous explanation of the different available concepts
and how to use them (declare, unit, uses, use, define-extension,
eval-when,
> ;;; foo.scm
> (declare (uses bar))
> (use bar)
You do not need the '(uses bar)'
If I leave it out, "csc bar.o foo.scm" gives the warning "extension
`bar' is currently not installed" and running the compiled foo results
in "Error: unbound variable: bar".
Best regards
Daniel Sadilek
On 1/10/07, Daniel Sadilek <[EMAIL PROTECTED]> wrote:
> > ;;; foo.scm
> > (declare (uses bar))
> > (use bar)
>
> You do not need the '(uses bar)'
If I leave it out, "csc bar.o foo.scm" gives the warning "extension
`bar' is currently not installed" and running the compiled foo results
in "Error:
felix winkelmann scripsit:
> Hi!
>
> Graham Fawcett has submitted the 256th egg:
>
> http://chicken.wiki.br/sqlora
Does this mean the egg list is closed?
Or are we shooting for 512 eggs now?
--
John Cowan http://ccil.org/~cowan[EMAIL PROTECTED]
In might the Feanorians / that swore the u
Hello,
this program causes a segmentation fault on Windows (cygwin) and Linux
with Chicken 2.5:
(define-record record value)
(print (make-record 1))
If I rename the record it works:
(define-record foo value)
(print (make-foo 1))
Best regards
Daniel Sadilek
__
On 1/10/07, felix winkelmann <[EMAIL PROTECTED]> wrote:
Hi!
Graham Fawcett has submitted the 256th egg:
http://chicken.wiki.br/sqlora
Thanks, Graham!
Thanks! I gladly accept the t-shirt. Since all Chicken contributors
deserve to share this honour, I invite you all to drop in and see me
--- whe
felix winkelmann scripsit:
> There is currently no simple way to have code that is made up of multiple
> modules, can be compiled into a single binary and at the same time
> can be transparently used in the interpreter (besides using `include').
Not that there's anything wrong with "include". My
On 1/10/07, Daniel Sadilek <[EMAIL PROTECTED]> wrote:
Hello,
this program causes a segmentation fault on Windows (cygwin) and Linux
with Chicken 2.5:
(define-record record value)
(print (make-record 1))
If I rename the record it works:
(define-record foo value)
(print (make-foo 1))
Uh oh -
On 1/10/07, John Cowan <[EMAIL PROTECTED]> wrote:
felix winkelmann scripsit:
> Hi!
>
> Graham Fawcett has submitted the 256th egg:
>
> http://chicken.wiki.br/sqlora
Does this mean the egg list is closed?
Or are we shooting for 512 eggs now?
That would be too Knuthian. But I can't come up with
On Wed, 10 Jan 2007 18:31:10 +0100 "felix winkelmann" <[EMAIL PROTECTED]> wrote:
> On 1/10/07, John Cowan <[EMAIL PROTECTED]> wrote:
> > felix winkelmann scripsit:
> > > Hi!
> > >
> > > Graham Fawcett has submitted the 256th egg:
> > >
> > > http://chicken.wiki.br/sqlora
> >
> > Does this mean the
Hi,
I've used PRINT, DISPLAY, WRITE, and NEWLINE in a thread created from
csi (the actual
thread-making function is in a .so). The thread is just a loop waiting
one second before the next
iteration. Strangely, I tried many times, and some times I have no
output but got NEWLINE. Another time I had
The various SSAX egg ports also use 'include'. The reason is the
source distributions are made up of a bunch of interrelated .scm
files, with a lot of internal procedures that you don't want exported
to the user. One option is to generate separate .so files and use a
module system to restrict th
Zbigniew scripsit:
> The various SSAX egg ports also use 'include'. The reason is the
> source distributions are made up of a bunch of interrelated .scm
> files, with a lot of internal procedures that you don't want exported
> to the user. One option is to generate separate .so files and use a
>
Apropos of nothing, if you surround the body of FAC with (let ((fac
fac)) ...) or even (let loop ((n n)) ...) then you avoid a global
lookup on FAC on every recursive call. This is the same as compiling
the file in block mode, except the latter doesn't work for exported
definitions. This is some
On 1/10/07, Zbigniew <[EMAIL PROTECTED]> wrote:
Apropos of nothing, if you surround the body of FAC with (let ((fac
fac)) ...) or even (let loop ((n n)) ...) then you avoid a global
lookup on FAC on every recursive call. This is the same as compiling
the file in block mode, except the latter doe
On 10 Jan 2007 15:44:27 -0200, Mario Domenech Goulart
<[EMAIL PROTECTED]> wrote:
On Wed, 10 Jan 2007 18:31:10 +0100 "felix winkelmann" <[EMAIL PROTECTED]> wrote:
> On 1/10/07, John Cowan <[EMAIL PROTECTED]> wrote:
> > felix winkelmann scripsit:
> > > Hi!
> > >
> > > Graham Fawcett has submitted
Hi!
> Or how about each 16th egg, for the next 256 eggs? (I'd be willing to
> buy a t-shirt or three, to help keep the egg-stream flowing.)
What about this: A random selected person of the group of people who
added an egg during 3 months. Or 4 months or whatever period of time.
That means that ev
On 1/10/07, Peter Busser <[EMAIL PROTECTED]> wrote:
What about this: A random selected person of the group of people who
added an egg during 3 months. Or 4 months or whatever period of time.
That means that everyone who adds an egg has a chance to get one.
+1.
--G
___
Graham Fawcett wrote:
On 1/10/07, Peter Busser <[EMAIL PROTECTED]> wrote:
What about this: A random selected person of the group of people who
added an egg during 3 months. Or 4 months or whatever period of time.
That means that everyone who adds an egg has a chance to get one.
+1.
Yep, I wa
On 1/10/07, Graham Fawcett <[EMAIL PROTECTED]> wrote:
On 1/10/07, Zbigniew <[EMAIL PROTECTED]> wrote:
> Apropos of nothing, if you surround the body of FAC with (let ((fac
> fac)) ...) or even (let loop ((n n)) ...) then you avoid a global
> lookup on FAC on every recursive call. This is the sam
On 1/10/07, minh thu <[EMAIL PROTECTED]> wrote:
Hi,
I've used PRINT, DISPLAY, WRITE, and NEWLINE in a thread created from
csi (the actual
thread-making function is in a .so). The thread is just a loop waiting
one second before the next
iteration. Strangely, I tried many times, and some times I h
2007/1/11, felix winkelmann <[EMAIL PROTECTED]>:
On 1/10/07, minh thu <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've used PRINT, DISPLAY, WRITE, and NEWLINE in a thread created from
> csi (the actual
> thread-making function is in a .so). The thread is just a loop waiting
> one second before the next
23 matches
Mail list logo
