gmane.lisp.scheme.stklos

STklos sometimes fails it's test suite

Vitaly Magerya — 2012-05-07T17:06:30

Hi Erick, hi everyone. It appears that STklos is subtly broken, as it
fails it's own test suite, but it only does so once in a while.

Here's how I build it (this is so you could easily reproduce the problem
by just copy-pasting this message to the command line):

    wget "http://www.stklos.net/download/stklos-1.10.tar.gz"
    tar xf stklos-1.10.tar.gz
    cd stklos-1.10
    ./configure --enable-threads=posix --with-provided-gc
    make
    make test

This may work at first, but if you'll repeat "make test" a few times
(20 times is usually enough), you'll see that some tests may fail. In
particular, on different occasions I've seen 3 errors:


==== Testing call/cc & dynamic-wind  ...                         failed
Errors found in this section:
test R5RS example on (let ((path '()) (c #f)) (let ((add (lambda (s)
(set! path (cons s path))))) (dynamic-wind (lambda () (add 'connect))
(lambda () (add (call-with-current-continuation (lambda (c0) (set! c
c0) 'talk1)))) (lambda () (add 'disconnect))) (if (< (length

STklos failes to run Silex without reporting an error

Sascha Ziemann — 2012-01-17T15:59:28

I am trying to use Silex with STklos. Silex is a lexer generator for Scheme:

http://www.iro.umontreal.ca/~dube/silex.tar.gz

But when I run Silex with STklos it fails to produce the lexer table
without reporting any error:

$ stklos
*   STklos version 1.10
 *  Copyright (C) 1999-2011 Erick Gallesio - Universite de Nice <eg< at >unice.fr>
* * [Linux-2.6.32-bpo.5-amd64-x86_64/pthread/readline/utf8]
stklos> (load "silex/silex.scm")
stklos> (lex "asn1.l" "stklos.scm")
#t
stklos>

The above session creates the file stklos.scm which contains the
lexer. I have attached the file. You can find at line 1756 a single
quote without any value. That is the bug.

Sorry for the big mail but the bug occurs only with big lexers.

When I run Silex with Gauche it works as expected. I have attached the
lexer generated by Gauche, which contains the correct value behind the
quote.

I have also attached my grammar file in order to reproduce the bug.

Silex stresses the Scheme interpreter by the number of arguments
passed to string-appe

Objects & SRFI-10: No Applicable Method

Taylor Venable — 2012-01-08T22:30:18

Hi there, I'm new to STklos and am trying to write my first little
program. I want to store objects into a file and read them out easily,
so looking at the manual I found an example of using write-object to
print out a representation ala SRFI-10. When I try this, however, it
doesn't work as I expected.

*   STklos version 1.10
 *  Copyright (C) 1999-2011 Erick Gallesio - Universite de Nice <eg< at >unice.fr>
* * [Linux-3.1.6-1-ARCH-x86_64/pthread/readline/utf8]
stklos> (define-class <foo> () ())
;; <foo>
stklos> (describe (make <foo>))
#[<foo> 1c00db0] is an an instance of class <foo>.
Slots are:
stklos> (define-reader-ctor 'make make)
stklos> (with-input-from-string "#,(make <foo>)" read)
**** Error:
error: no applicable method for #[<generic> make-instance (1)]
in call (make-instance <foo>)
        (type ",help" for more information)
stklos> (make-instance <foo>)
#[<foo> 1c2c240]

What am I doing wrong? Thanks!

--
Taylor C. Venable
http://metasyntax.net/
_____________________________________________

Objects & SRFI-10: No Applicable Method

Taylor Venable — 2012-01-08T22:30:18

Hi there, I'm new to STklos and am trying to write my first little
program. I want to store objects into a file and read them out easily,
so looking at the manual I found an example of using write-object to
print out a representation ala SRFI-10. When I try this, however, it
doesn't work as I expected.

*   STklos version 1.10
 *  Copyright (C) 1999-2011 Erick Gallesio - Universite de Nice <eg< at >unice.fr>
* * [Linux-3.1.6-1-ARCH-x86_64/pthread/readline/utf8]
stklos> (define-class <foo> () ())
;; <foo>
stklos> (describe (make <foo>))
#[<foo> 1c00db0] is an an instance of class <foo>.
Slots are:
stklos> (define-reader-ctor 'make make)
stklos> (with-input-from-string "#,(make <foo>)" read)
**** Error:
error: no applicable method for #[<generic> make-instance (1)]
in call (make-instance <foo>)
        (type ",help" for more information)
stklos> (make-instance <foo>)
#[<foo> 1c2c240]

What am I doing wrong? Thanks!

--
Taylor C. Venable
http://metasyntax.net/
_____________________________________________

Objects & SRFI-10: No Applicable Method

Taylor Venable — 2012-01-08T22:30:18

Hi there, I'm new to STklos and am trying to write my first little
program. I want to store objects into a file and read them out easily,
so looking at the manual I found an example of using write-object to
print out a representation ala SRFI-10. When I try this, however, it
doesn't work as I expected.

*   STklos version 1.10
 *  Copyright (C) 1999-2011 Erick Gallesio - Universite de Nice <eg< at >unice.fr>
* * [Linux-3.1.6-1-ARCH-x86_64/pthread/readline/utf8]
stklos> (define-class <foo> () ())
;; <foo>
stklos> (describe (make <foo>))
#[<foo> 1c00db0] is an an instance of class <foo>.
Slots are:
stklos> (define-reader-ctor 'make make)
stklos> (with-input-from-string "#,(make <foo>)" read)
**** Error:
error: no applicable method for #[<generic> make-instance (1)]
in call (make-instance <foo>)
        (type ",help" for more information)
stklos> (make-instance <foo>)
#[<foo> 1c2c240]

What am I doing wrong? Thanks!

--
Taylor C. Venable
http://metasyntax.net/
_____________________________________________

[Announce] STklos-1.10 release

Erick Gallesio — 2011-12-31T17:14:54

This is an announce for the 1.10 release of STklos.


STklos is a free Scheme system compliant with the languages features
defined in R5RS. The aim of this implementation is to be fast as well
as light. The implementation is based on an ad-hoc Virtual
Machine. STklos can also be compiled as a library and embedded in an
application.

The salient points of STklos are:

    * an efficient and powerful object system based on CLOS 
      providing
          o Multiple Inheritance,
          o Generic Functions,
          o Multi-methods
          o an efficient MOP (Meta Object Protocol)
    * a simple to use module system
    * a full tower of numbers implementation, as defined in R5RS,
    * easy connection to the GTK+ toolkit,
    * a Perl compatible regular expressions thanks to the PCRE 
      package,
    * easily extensible with its ScmPkg mechanism,
    * it implements properly tail recursive calls.

This version brings the support of UTF-8 encoding and begins to support some (future) R7RS traits:

    *

STklos update

Erick Gallesio — 2011-08-28T17:37:39

Hi,

I have committed a large set of modifications to STklos that were in a 
private development tree. The modifications permits mainly to support 
UTF-8 encoding in strings. There are also patches to support the future 
R7RS version of Scheme (small language). There are some things that 
still need to be done to have a new version, but current code should be 
usable. If you don't want to use UTF-8 encoding, you can use the 
--utf8-encoding=no option.

If you are interested, the code is available at 
http://stklos.net/hg/hgweb.cgi/archive/tip.tar.gz

A bientôt

FFI docs and examples

nitralime — 2011-01-28T11:22:39

Hi folks!

Is there a better (resp. more detailed) documentation of FFI?
Do you know examples of binding external libraries which
can be used to get familiar with FFI?

Regards
Nik
_______________________________________________
STklos mailing list
STklos< at >email.essi.fr
http://email.essi.fr/mailman/listinfo/stklos

parameterize

Joo ChurlSoo — 2011-01-07T00:42:42

The following parameterize behavior seems to be wrong.

(let ((f (make-parameter 'a))
      (path '())
      (c #f))
  (let ((add (lambda () (set! path (cons (f) path)))))
    (add)
    (parameterize ((f 'b))
   (call-with-current-continuation (lambda (c0) (set! c c0)))
   (add) (f 'c) (add))
    (f 'd)
    (add)
    (if (< (length path) 5)
 (c 'end)
 (reverse path))))
 (a b c d b c d) ;This answer seems to be wrong. (cf.) (a b c d c c d)

[Announce] STklos-1.01 release

2010-12-30T19:04:57

This is an announce for the 1.01 release of STklos.


STklos is a free Scheme system compliant with the languages features
defined in R5RS. The aim of this implementation is to be fast as well
as light. The implementation is based on an ad-hoc Virtual
Machine. STklos can also be compiled as a library and embedded in an
application.

The salient points of STklos are:

    * an efficient and powerful object system based on CLOS 
      providing
          o Multiple Inheritance,
          o Generic Functions,
          o Multi-methods
          o an efficient MOP (Meta Object Protocol)
    * a simple to use module system
    * a full tower of numbers implementation, as defined in R5RS,
    * easy connection to the GTK+ toolkit,
    * a Perl compatible regular expressions thanks to the PCRE 
      package,
    * easily extensible with its ScmPkg mechanism,
    * it implements properly tail recursive calls.

This release is mainly a maintenance version. Changes in this version:
     * Documentation update
     *

Nested quasiquotation bug

Rock — 2010-12-14T23:48:17

I think I've discovered a bug here.

The following:

``(,< at >(append ,< at >'((list 2 3) (list 5 7))))

should produce:

(quasiquote ((unquote-splicing (append (list 2 3) (list 5 7)))))

as it does correctly with Guile.

But with stklos 1.0, you get:

`(,< at >(append ,< at >'((list 2 3) (list 5 7))))

As you can see, it doesn't evaluate the internal unquote-splicing at all!

Thank you.

Internat d'Été?

Michael Feyereisen — 2010-12-11T18:20:33

Cher Erick,

STklos m'interesse beaucoup, et j'aimerais savoir s'il serait possible
de faire un internat à l'Université de Nice cet été, afin par exemple
de vous aider à écrire de la documentation, voire du code (en Scheme
ou en C).

Merci beaucoup,

Michael Feyereisen

Imperial College London
Department of Physics

Can't import SRFI 27 via require-extension

Vitaly Magerya — 2010-11-07T13:17:03

It appears that you can't import SRFI 27 via require-extension,
only through require. Here's an example:

    stklos> (require-extension (srfi 27))
    stklos> default-random-source
    **** Error:
    %execute: variable `default-random-source' unbound
            (type ",help" for more information)

With require on the other hand it works as expected:

    stklos> (require "srfi-27")
    "srfi-27"
    stklos> default-random-source
    #[<random-source> 8247a98]

It appears that SRFI 27 is listed as imported by default in SRFI 0
features list. The fix is this (it's trivial, so I'm sending it
inline):
  
diff --git a/lib/srfi-0.stk b/lib/srfi-0.stk
--- a/lib/srfi-0.stk
+++ b/lib/srfi-0.stk
< at >< at > -61,7 +61,7 < at >< at >
     ;; srfi-24; ....... withdrawn
     ;; srfi-25; Multi-dimensional Arrays
     (srfi-26 "srfi-26"); Specialize Param without Currying
-    ((srfi-27 random)); Sources of Random Bits
+    ((srfi-27 random)"srfi-27"); Sources of Random Bits
     srfi-28; Basic Format Strings
     ;; sr

Broken process functions

Vitaly Magerya — 2010-11-06T20:44:59

It appears that process-kill, process-stop and process-continue
functions are broken. Here's an example:

    stklos> (process-kill (run-process "cat"))
    **** Error:
    process-signal: bad signal name `|SIGTERM|'
            (type ",help" for more information)

The function `process-kill' is defined in lib/process.stk like this:

    (define (process-kill proc) (process-signal proc 'SIGTERM))

My conjecture is that boot code is executed in a case-sensitive
environment, and since src/signal.c contains signal names in lower
case, process-signal fails to find signal "SIGTERM" (it can find
"sigterm" instead).

The trivial fix is to go through lib/process.stk and to lower the
case of SIGTERM, SIGSTOP and SIGCONT in process-signal invocations.
A more complex fix would be to make sure the boot code is compiled
with case-folding enabled, but I have no idea how to do that.

One more problem is that the documentation refers to a non-existent
function "process-send-signal". It should be "process-signal" instead.

Tail patterns in syntax-rules

Vitaly Magerya — 2010-10-21T09:08:46

Hi, all. Erick, is there any interest in supporting tail patterns in
syntax-rules a la SRFI 46 (and R6RS)? If so, I've got a patch at [1]
that implements them.

Note that currently STklos actually allows a different (incompatible)
kind of tail patterns, like this:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))))

    (test 1 2 stop 3 4)  ===>  (1 2 / 3 4)

But I don't think anyone uses this extension, as it is broken:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))
        ((test a ...) '(a ...))))

    (test 1 2 3 4)  ===>
    **** Error:
    mbe:split-at-ellipsis: bad-arg
    (type ",help" for more information)

Although you can easily fix this behavior, SRFI 46-style tail
patterns seem like a better bet because many other implementations
already support them.

Here's an example of what you can do with the patch applied:

    (define-syntax test
      (syntax-rules ()
        ((test a ... b c) '(

Tail patterns in syntax-rules

Vitaly Magerya — 2010-10-20T22:49:32

Hi, all. Erick, is there any interest in supporting tail patterns in
syntax-rules a la SRFI 46 (and R6RS)? If so, I've got a patch at [1]
that implements them.

Note that currently STklos actually allows a different (incompatible)
kind of tail patterns, like this:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))))

    (test 1 2 stop 3 4)  ===>  (1 2 / 3 4)

But I don't think anyone uses this extension, as it is broken:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))
        ((test a ...) '(a ...))))

    (test 1 2 3 4)  ===>
    **** Error:
    mbe:split-at-ellipsis: bad-arg
    (type ",help" for more information)

Although you can easily fix this behavior, SRFI 46-style tail
patterns seem like a better bet because many other implementations
already support them.

Here's an example of what you can do with the patch applied:

    (define-syntax test
      (syntax-rules ()
        ((test a ... b c) '(

Tail patterns in syntax-rules

Vitaly Magerya — 2010-10-21T09:08:46

Hi, all. Erick, is there any interest in supporting tail patterns in
syntax-rules a la SRFI 46 (and R6RS)? If so, I've got a patch at [1]
that implements them.

Note that currently STklos actually allows a different (incompatible)
kind of tail patterns, like this:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))))

    (test 1 2 stop 3 4)  ===>  (1 2 / 3 4)

But I don't think anyone uses this extension, as it is broken:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))
        ((test a ...) '(a ...))))

    (test 1 2 3 4)  ===>
    **** Error:
    mbe:split-at-ellipsis: bad-arg
    (type ",help" for more information)

Although you can easily fix this behavior, SRFI 46-style tail
patterns seem like a better bet because many other implementations
already support them.

Here's an example of what you can do with the patch applied:

    (define-syntax test
      (syntax-rules ()
        ((test a ... b c) '(

Tail patterns in syntax-rules

Vitaly Magerya — 2010-10-20T22:49:32

Hi, all. Erick, is there any interest in supporting tail patterns in
syntax-rules a la SRFI 46 (and R6RS)? If so, I've got a patch at [1]
that implements them.

Note that currently STklos actually allows a different (incompatible)
kind of tail patterns, like this:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))))

    (test 1 2 stop 3 4)  ===>  (1 2 / 3 4)

But I don't think anyone uses this extension, as it is broken:

    (define-syntax test
      (syntax-rules (stop)
        ((test a ... stop b ...) '(a ... / b ...))
        ((test a ...) '(a ...))))

    (test 1 2 3 4)  ===>
    **** Error:
    mbe:split-at-ellipsis: bad-arg
    (type ",help" for more information)

Although you can easily fix this behavior, SRFI 46-style tail
patterns seem like a better bet because many other implementations
already support them.

Here's an example of what you can do with the patch applied:

    (define-syntax test
      (syntax-rules ()
        ((test a ... b c) '(

[Announce] STklos-1.00 release

2010-08-11T13:47:08

This is an announce for the 1.00 release of STklos.


STklos is a free Scheme system compliant with the languages features
defined in R5RS. The aim of this implementation is to be fast as well
as light. The implementation is based on an ad-hoc Virtual
Machine. STklos can also be compiled as a library and embedded in an
application.

The salient points of STklos are:

    * an efficient and powerful object system based on CLOS 
      providing
          o Multiple Inheritance,
          o Generic Functions,
          o Multi-methods
          o an efficient MOP (Meta Object Protocol)
    * a simple to use module system
    * a full tower of numbers implementation, as defined in R5RS,
    * easy connection to the GTK+ toolkit,
    * a Perl compatible regular expressions thanks to the PCRE 
      package,
    * easily extensible with its ScmPkg mechanism,
    * it implements properly tail recursive calls.

The version 1.00 is finally here (work on STklos started 10 years
before ...).  The main difference with

Problems with building latest sources

Vitaly Magerya — 2010-05-07T12:41:00

Hi, all. I've got two problems with building the latest STklos sources
on FreeBSD 8.0 i386.

1. The default case for OS_NAME_VERSION at configure.ac:107 does not
work: it sets the variable to $v, ignoring $OS. For example on my system
$OS_NAME_VERSION is "8_0________". This leads to problems when
$OS_NAME_VERSION is injected as a variable name to src/extraconf.h,
since variable names can't start with digits.

Changing "$OS_$v" to "$OS\_$v" fixes the issue for me.

2. When the check for libintl.h at configure.ac:27 succeeds, autoconf
sets HAVE_LIBINTL_H to 1. This enables gettext at src/gnu-getopt.c:139.
Since you don't link against gettext libraries, linking of stklos binary
fails with undefined reference to libintl_gettext.

It appears that only gnu-getopt.c uses gettext, so I think it's safe to
remove libintl.h check from configure.ac and HAVE_LIBINTL_H check from
gnu-getopt.c completely. At least that works for me.

Finally, not a build problem, but still:

    stklos> (let () (define x 0))
    **** Error

stklos.org, FFI, new release, etc

Vitaly Magerya — 2010-03-15T14:03:38

Hi, Erick. I've got a few miscellaneous requests and questions.

1. For some time now stklos.org domain belongs to someone else, so
   the references to it in pkgman/params.stk should be updated.
   Currently stklos-pkg can't find it's own servers with default
   settings.

2. Please add the FreeBSD console "cons25" to the list of terminals
   with ANSI colors at lib/repl.stk:47. I've tested it, and the colors
   work on all current FreeBSD releases.

3. In utils/stklos-install:69 wget is used to retrieve the package.
   Can you conditionally use wget *or* fetch depending on which is
   available, so that it would work on FreeBSD machines without wget?

4. If I need to pass a structure to a C function via FFI, and read
   what it stores there, should I allocate it via malloc or GC_malloc?
   Or is there a Scheme-level function to do it?

5. Are there plans to support structure passing directly in the FFI?
   Something like SRFI 74-style blobs directly passable to C would
   be a great start.

6. Finally, I s