<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.lisp.guile.user">
    <title>gmane.lisp.guile.user</title>
    <link>http://blog.gmane.org/gmane.lisp.guile.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9474"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9471"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9469"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9466"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9458"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9453"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9443"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9435"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9429"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9411"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9402"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9396"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9394"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9393"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9386"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9377"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9376"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9373"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9371"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.lisp.guile.user/9367"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9474">
    <title>Extending a GTK+ Application with Guile</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9474</link>
    <description>&lt;pre&gt;Hello Guilers.

I'm currently writing some prototype code before starting a project and
have a few questions that I hope some of you may be able to answer.

My intent is to add guile as a method of [optionally, at build time]
extending a GTK+ application. With the addition of being able to run
guile scripts I hope to provide a guile-shell to give real-time
interactive power. First a question of program architecture;

As the guile extensions are optional I run GTK on a main thread and the
shell on a second pthread. I connect the shell through a PTY to the
virtual terminal widget.

I apologise to those with mail clients not using monospace fonts.

  THREAD1            THREAD2
 ---------           -------
| GTK     |   pty   | guile |
|     VTE |&amp;lt;-------&amp;gt;| shell |
|  -----  |          -------
| guile   |
|  scripts|
 ---------

0) Is there anything wrong with this architecture?

   a) Is it valid to use both scm_shell and other guile code at the same
   time or is scm_shell designed to run in isolation?

   b) Not related to guile but while I'm here I may as well ask. Is there
   a more appropriate GTK+ method of communicating (STDIN, STDOUT,
   STERR) with the running application (to replace the VTE above)

1) scm_shell allows the `,q' command (and probably some other exit
routes) which kills the whole application. Is there a way to present a
shell (or similar subset) without the ability to exit?

2) Thinking of portability, is guile running on Windows (without
cygwin), to justify the claim of 'ubiquitous'?

Happy Hacking,
Kevin Fletcher.



&lt;/pre&gt;</description>
    <dc:creator>Kevin J. Fletcher</dc:creator>
    <dc:date>2012-05-24T19:11:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9471">
    <title>letter occurence in a text</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9471</link>
    <description>&lt;pre&gt;
hello my problem is to count occurence of letter in a text and come out with
an assoc-list like
'((a.16) (b.10) ... (z.5))
i started a fee function but they don't work so please help me

;; an alist
(define lettre '((""."") ) )
(define lettre2 '(("a". 1) ("b". 1) ("c". 1) ) )

;; this function take a key and an alist
;; add the key to the alist if it is not a space,a newline,and does not
already exist
;; update the value of the given key
(define (lettre-test x alist)
(cond ((and 
          ( and (not (char=?  x #\space))(not (char=?  x #\newline)))   
          (eq? (assoc (make-string 1 x) alist) #f))  
          (set! alist
          (assoc-set! alist (make-string 1 x) 0 )))
          ((char=?  x #\space) '())
          ((char=?  x #\newline) '()) 
           (else
           (set! alist   
       (assoc-set! alist (make-string 1 x) (+ (assoc-ref alist
(make-string 1 x)) 1))))))

;; this function open a file
;; read the caracter and count the occurence of each character
(define (compte-char source alist)
(let ((p (open-port source)))
  (let f ((x (read-char p)))
    (cond ((eof-object? x)
        (begin
          (close-input-port p)
          '()))        
         (else
        (cons (lettre-test x alist) (f (read-char p))))))))
&lt;/pre&gt;</description>
    <dc:creator>nrichard</dc:creator>
    <dc:date>2012-05-22T14:26:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9469">
    <title>guile-lib test failed</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9469</link>
    <description>&lt;pre&gt;With guile 2.0.5 installing guile-lib 0.2.1 ./configure and make
run without problems. But "make check" say one test failed. See
attached file. There are some spanish messages. I don't know how
configure it to display all in english. Regards.&lt;/pre&gt;</description>
    <dc:creator>Germán A. Arias</dc:creator>
    <dc:date>2012-05-20T12:31:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9466">
    <title>dynamic ffi and C struct</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9466</link>
    <description>&lt;pre&gt;Hello,

Is it possible to use the current dynamic ffi to call a C function
whose parameter is a C struct (not a pointer to a C struct) ?

I cannot find much about it in the documentation.  After a brief look
at the source of foreign.c of guile, I found guile actually does some
parsing of nested argument list for `pointer-&amp;gt;procedure' and generates
compound ffi types.  But I don't know the right data structure to give
when actually calling the foreign function.

For example, what should I do for the following function?

typedef struct {
  int dat[2];
} foo_t;

int func ( foo_t arg );

&lt;/pre&gt;</description>
    <dc:creator>cong gu</dc:creator>
    <dc:date>2012-05-19T11:32:07</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9458">
    <title>[ANN] Guile-Reader 0.6</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9458</link>
    <description>&lt;pre&gt;Version 0.6 of Guile-Reader for Guile 2.0.x and 1.8.x is now available.
This release adds new features, most notably Guile 2.0 and Unicode support.

  http://dl.sv.nongnu.org/releases/guile-reader/guile-reader-0.6.tar.gz
  http://dl.sv.nongnu.org/releases/guile-reader/guile-reader-0.6.tar.gz.sig

SHA1 sums:

  aaedfe0c656775ba895b02293481a7d7c36b1f7e  guile-reader-0.6.tar.gz
  284404e6403d396819ff4e060d4a496f66727d8f  guile-reader-0.6.tar.gz.sig

Documentation is available from:

  http://www.nongnu.org/guile-reader/

Guile-Reader is a reader creation framework for Guile.  It can be
thought of as an alternative to Guile's built-in reader.  The purpose of
Guile-Reader is to allow for the creation of readers for different
variants of the Scheme/Lisp syntax.  Its design allows the re-use and
composition of various parts of a lexer called “token readers”.  It
comes with a library of re-usable token readers that can be used to
build a Scheme reader with various extensions.  For instance, syntax
extensions for DSSSL keywords, SRFI-30 block comments, SRFI-62 S-exp
comments, square-bracket S-exps, and brace S-exps are provided and
readily usable through the ‘make-alternate-guile-reader’ procedure.

Additionally, Guile-Reader aims to improve on Guile's reader sub-system
by allowing for the coexistence of several, potentially incompatible,
readers within a single Guile program.  In particular, it provides a
“confinement” mechanism that confines changes made via ‘read-set!’ and
‘read-hash-extend’ to the calling module.

New in Guile-Reader 0.6

  * Guile-Reader is now distributed under GPLv3 or later (instead of
    GPLv2 or later).

  * New token reader for R6RS-style syntax quotes: #', #`, and #,.

  * `make-guile-reader' returns a reader that understands SRFI-62
    s-exp comments, R6RS-style syntax quotes, and s-exps introduced by
    square brackets.  All these are supported by default by `read' in
    Guile 2.0.

  * On Guile 2.0, non-ASCII Unicode symbols, strings, characters, and
    Skribe-expressions are correctly read.

  * On Guile 2.0, Scheme source files are compiled and installed.

  * Bugs fixed

    * Add support for rationals in the number token reader.

    * Provide replacement for some `scm_i_' functions and other
      internals no longer accessible in Guile 1.9+.

    * Adjust packaging so that it works with Guile 1.9+.

Ludovic.
&lt;/pre&gt;</description>
    <dc:creator>Ludovic Courtès</dc:creator>
    <dc:date>2012-05-08T21:06:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9453">
    <title>http-read with cookie</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9453</link>
    <description>&lt;pre&gt;Hello,

There is http-get in Guile and will be http-put, then what's the next? I
think the method using cookie and handling https. I had thought that I'd be
able to read contents of a web page needing login when I had read http-put
of Greg Benison,
http://lists.gnu.org/archive/html/guile-user/2012-04/msg00012.html .
How naive am I.

I recognize we need handling https because most login process of web pages
require it but have no idea of it now. During some trial, I made a very
little effort and want to share it. Of course, there shold be the better
way; I'm a newbie yet.

1.1 Exampe of http-get:

(receive (header body)
    (http-get (string-&amp;gt;uri "http://code.google.com/"))
  (display header)
  (newline))
(receive (header body)
    (http-get (string-&amp;gt;uri "http://code.google.com/"))
  (display header)
  (newline))

1.2 Output of above example:

#&amp;lt;&amp;lt;response&amp;gt; version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #&amp;lt;date nanosecond: 0 second: 41 minute: 20 hour: 23 day: 5
month: 5 year: 2012 zone-offset: 0&amp;gt;) (date . #&amp;lt;date nanosecond: 0 second: 9
minute: 3 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0&amp;gt;) (expires .
#&amp;lt;date nanosecond: 0 second: 9 minute: 3 hour: 7 day: 6 month: 5 year: 2012
zone-offset: 0&amp;gt;) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=6d783c184a55e937:TM=1336287789:LM=1336287789:S=p7v3fPvc55hTb15k;
expires=Tue, 06-May-2014 07:03:09 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #&amp;lt;closed: file
0&amp;gt;&amp;gt;
#&amp;lt;&amp;lt;response&amp;gt; version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #&amp;lt;date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0&amp;gt;) (date . #&amp;lt;date nanosecond: 0 second:
10 minute: 3 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0&amp;gt;) (expires .
#&amp;lt;date nanosecond: 0 second: 10 minute: 3 hour: 7 day: 6 month: 5 year:
2012 zone-offset: 0&amp;gt;) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=e7e80585317f6678:TM=1336287790:LM=1336287790:S=PQWgTbaxsZyIqeVy;
expires=Tue, 06-May-2014 07:03:10 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #&amp;lt;closed: file
0&amp;gt;&amp;gt;

1.3 Discussion about above output:
1) We need a web page using cookie. I picked http://code.google.com/ ; it
set PREF cookie once unlike http://www.google.com/ twice.
2) Example displays two headers, so the output is two line. In the first
line, http://code.google.com/ replied with set-cookie PREF. You may want to
send cookie header when the next request. If not so, the server would
re-send set-cookie PREF again as seen in second line.
3) Cookie header is essential when making a session. In above example, of
course, actually no need to making a session, so no need cookie, it's just
a test.

2.1 Example of http-read:

(receive (header body)
    (http-read "http://code.google.com/")
  (display header)
  (newline))
(receive (header body)
    (http-read "http://code.google.com/")
  (display header)
  (newline))

2.2 Output of above example:

#&amp;lt;&amp;lt;response&amp;gt; version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #&amp;lt;date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0&amp;gt;) (date . #&amp;lt;date nanosecond: 0 second:
58 minute: 23 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0&amp;gt;) (expires
. #&amp;lt;date nanosecond: 0 second: 58 minute: 23 hour: 7 day: 6 month: 5 year:
2012 zone-offset: 0&amp;gt;) (cache-control private (max-age . 3600))
(x-content-type-options . "nosniff") (set-cookie .
"PREF=ID=8253d36f6bcd8b99:TM=1336289038:LM=1336289038:S=xDYcthWhrVAC2asa;
expires=Tue, 06-May-2014 07:23:58 GMT; path=/; domain=.google.com") (server
. "codesite_static_content") (x-xss-protection . "1; mode=block")
(x-frame-options . "SAMEORIGIN") (connection close)) port: #&amp;lt;closed: file
0&amp;gt;&amp;gt;
#&amp;lt;&amp;lt;response&amp;gt; version: (1 . 1) code: 200 reason-phrase: "OK" headers: ((vary
accept-language cookie referer) (content-type text/html (charset .
"ISO-8859-1")) (etag "fe11bb5c119a4c282ecbc99fc66bc7f1" . #t)
(last-modified . #&amp;lt;date nanosecond: 0 second: 46 minute: 32 hour: 4 day: 6
month: 5 year: 2012 zone-offset: 0&amp;gt;) (date . #&amp;lt;date nanosecond: 0 second:
58 minute: 23 hour: 7 day: 6 month: 5 year: 2012 zone-offset: 0&amp;gt;) (expires
. #&amp;lt;date nanosecond: 0 second: 58 minute: 23 hour: 8 day: 6 month: 5 year:
2012 zone-offset: 0&amp;gt;) (cache-control public (max-age . 3600))
(x-content-type-options . "nosniff") (server . "codesite_static_content")
(x-xss-protection . "1; mode=block") (x-frame-options . "SAMEORIGIN")
(connection close)) port: #&amp;lt;closed: file 0&amp;gt;&amp;gt;

2.3 Discussion about above output:

1) http-read can accept a string URL as it's first argument; of course, it
can accept a uri object like result of string-&amp;gt;uri.
2) In the first line, the server replied with set-cookie PREF like 1.2 but
there is no second set-cookie PREF in the second line because http-read had
sent cookie header when second request.

I had attatched a code of http-read.
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-05-06T07:39:27</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9443">
    <title>Unbound variable: cond-expand-provide</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9443</link>
    <description>&lt;pre&gt;Hello,

I thought cond-expand-provide be available in everywhere but saw a compile
error, "ERROR: In procedure module-lookup: Unbound variable:
cond-expand-provide". I don't know why this is happening; do you have any
idea or comments? Thanks in advance.

test-load in attatched archive file is a script to load srfi-64.scm. This
is very simple like this:

#!/usr/bin/guile \
-e main -s
!#
;;; Set %load-path
(eval-when
 (compile load eval)
 (let ((%current-filename (current-filename)))
   (if %current-filename
       (let ((%current-path (dirname %current-filename)))
         (if (not (memq %current-path %load-path))
             (add-to-load-path %current-path))))))
;;; Fake main for "-e main" option of Guile
(define (main . args)
  (let ((module (resolve-module '(test-load))))
    (apply (module-ref module 'main) args)))
;;; Module
(define-module (test-load)
  #:use-module (srfi srfi-64)
  #:export (main))
;;; Real main
(define (main args) #f)

In srfi-64.scm, I had used "(cond-expand-provide (current-module)
'(srfi-64))" like other srfi modules.

Frist execution of above script is fine:
  $ ./test-load
  ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
  ;;;       or pass the --no-auto-compile argument to disable.
  ;;; compiling /home/sunjoong/test-load/./test-load
  ;;; compiling /home/sunjoong/test-load/srfi/srfi-64.scm
  ;;; compiled
/home/sunjoong/.cache/guile/ccache/2.0-LE-4-2.0/home/sunjoong/test-load/srfi/srfi-64.scm.go
  ;;; compiled
/home/sunjoong/.cache/guile/ccache/2.0-LE-4-2.0/home/sunjoong/test-load/test-load.go

In second execution, I saw "Unbound variable: cond-expand-provide":
  $ ./test-load
  Backtrace:
  In ice-9/boot-9.scm:
   149: 17 [catch #t #&amp;lt;catch-closure 96a8540&amp;gt; ...]
   157: 16 [#&amp;lt;procedure 96708c0 ()&amp;gt;]
  In unknown file:
     ?: 15 [catch-closure]
  In ice-9/boot-9.scm:
    63: 14 [call-with-prompt prompt0 ...]
  In ice-9/eval.scm:
   407: 13 [eval # #]
  In ice-9/boot-9.scm:
  2111: 12 [save-module-excursion #&amp;lt;procedure 965d040 at
ice-9/boot-9.scm:3646:3 ()&amp;gt;]
  3653: 11 [#&amp;lt;procedure 965d040 at ice-9/boot-9.scm:3646:3 ()&amp;gt;]
  In unknown file:
     ?: 10 [load-compiled/vm
"/home/sunjoong/.cache/guile/ccache/2.0-LE-4-2.0/home/sunjoong/test-load/test-load.go"]
  In /home/sunjoong/test-load/./test-load:
    20: 9 [#&amp;lt;procedure 96b6210 ()&amp;gt;]
  In ice-9/boot-9.scm:
  2667: 8 [define-module* (test-load) #:filename ...]
  2642: 7 [resolve-imports (((srfi srfi-64)))]
  2580: 6 [resolve-interface (srfi srfi-64) #:select ...]
  2505: 5 [#&amp;lt;procedure 966df60 at ice-9/boot-9.scm:2493:4 (name #:optional
autoload version #:key ensure)&amp;gt; # ...]
  2772: 4 [try-module-autoload (srfi srfi-64) #f]
  2111: 3 [save-module-excursion #&amp;lt;procedure 96abcf0 at
ice-9/boot-9.scm:2773:17 ()&amp;gt;]
  2783: 2 [#&amp;lt;procedure 96abcf0 at ice-9/boot-9.scm:2773:17 ()&amp;gt;]
  In unknown file:
     ?: 1 [primitive-load-path "srfi/srfi-64" #f]
  In srfi/srfi-64.scm:
    85: 0 [#&amp;lt;procedure 967d020 ()&amp;gt;]

  srfi/srfi-64.scm:85:2: In procedure #&amp;lt;procedure 967d020 ()&amp;gt;:
  srfi/srfi-64.scm:85:2: In procedure module-lookup: Unbound variable:
cond-expand-provide
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-05-03T15:50:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9435">
    <title>Working http-get example and still unsolved problem</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9435</link>
    <description>&lt;pre&gt;Hello,

It's 1st day of May, a new month; I thought it would be better to summarize
some issues of http-get. This post include 3 examples; working, half
working and not working because of implementation of declare-uri-header!

Example 1 - working

(use-modules (srfi srfi-8)
             ((web uri)    #:select (string-&amp;gt;uri))
             ((web client) #:select (http-get)))

(set-port-encoding! (current-output-port) "UTF-8")
(fluid-set! %default-port-encoding "UTF-8")

(receive (res-headers res-body)
    (http-get (string-&amp;gt;uri "http://www.gnu.org/software/guile/"))
  (display res-body)
  (newline))

1. receive is a macro to receive multi valued return of a certain
procedure. http-get returns two values; headers of a web page and content
of that.

2. (fluid-set! %default-port-encoding "UTF-8") is not needed in above case;
codeset of http://www.gnu.org/software/guile/ is UTF-8 and above example
only display it. I think it is a good habit to append this line if you want
to use some other tools like html-&amp;gt;sxml of guile-lib.

3. (set-port-encoding! (current-output-port) "UTF-8") is not needed in
above case; codeset of http://www.gnu.org/software/guile/ is UTF-8 and
written in plain english. I think it is a good habit to append this line if
you want to display the content of web page.

Example 2 - half working

(receive (res-headers res-body)
    (http-get (string-&amp;gt;uri "http://www.gnu.org/home.en.html"))
  (display res-body)
  (newline))

1. http-get of current stable version, 2.0.5,  of Guile does not
support "Chunked Encoding."
2. You should apply patches of Ian Price's,
http://lists.gnu.org/archive/html/guile-user/2011-11/msg00011.html , if
this case.

Example 3 - not working

(receive (res-headers res-body)
    (http-get (string-&amp;gt;uri "http://www.gnu.org/home.html")
              #:extra-headers
              (acons 'Accept-Language "en-US" '()))
  (display res-body)
  (newline))

1. http://www.gnu.org/home.html replay with the contents of
http://www.gnu.org/home.en.html .
2. Its Content-Location header is home.en.html, not
http://www.gnu.org/home.en.html ; it is a relative URI, not absolute URI.
There is no solution on current Guile if this case. Avoid this case and use
a real web page like http://www.gnu.org/home.en.html .
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-05-01T15:20:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9429">
    <title>Problem with guile on Dragora</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9429</link>
    <description>&lt;pre&gt;Hi, I'm testing guile 2.0.5 in a new system (www.dragora.org). The
compilation seems OK. But when I run guile I get:

bash-4.2$ guile
Backtrace:
In ice-9/boot-9.scm:
 149: 2 [catch #t #&amp;lt;catch-closure 830e510&amp;gt; ...]
 157: 1 [#&amp;lt;procedure 82dd8c0 ()&amp;gt;]
In unknown file:
   ?: 0 [catch-closure]

ERROR: In procedure catch-closure:
ERROR: Throw to key `decoding-error' with args `("scm_from_stringn"
"input locale conversion error" 22 #vu8(103 117 105 108 101))'.
bash-4.2$ 

Attached the config.log. Thanks in advance.&lt;/pre&gt;</description>
    <dc:creator>Germán A. Arias</dc:creator>
    <dc:date>2012-05-01T05:53:59</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9411">
    <title>I'm looking for a method of converting a string's character encoding</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9411</link>
    <description>&lt;pre&gt;Hello,

I'm looking for a method of converting a string's character encoding from a
certain codeset to utf-8. I know the string of Guile uses utf-8 and (read
(open-bytevector-input-port (string-&amp;gt;utf8 "hello"))) returns "hello" . But
what if the string "hello" be encoded not utf-8 and you want to get utf-8
converted string? What I want is like iconv.

Background;
#:decode-body? keyword of http-get seems not to work properly; I should
set #:decode-body? to false value and decode the contents body string
manually. If a web page's charset be utf-8, there be no problem. If not, a
problem occurs. decode-response-body of (web client) call decode-string
with web page's charset. But real charset of bytevector is iso-8859-1,
not web page's charset. If so, you should not let http-get
use decode-response-body.

After getting response-body with bytevector form, you should decode it with
"iso-8859-1" like decode-string's manner. Then you'll get web page's
contents body string; it's charset is what you see in response header.

Now, I need to convert this contents body string to utf-8 but I don't know
how. I think it would be with port i/o.

Thanks.
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-27T21:13:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9402">
    <title>read-response-body of (web response) depends on Content-Length but ...</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9402</link>
    <description>&lt;pre&gt;Hello,

I cannot solve
http://lists.gnu.org/archive/html/guile-user/2012-04/msg00034.html yet.
This is a potentially related problem but I'm not sure;

(use-modules ((srfi srfi-11) #:select (let-values))
             ((web uri)      #:select (string-&amp;gt;uri))
             ((web client)   #:select (http-get)))
(let-values (((res-headers res-body)
              (http-get (string-&amp;gt;uri "http://www.gnu.org/home.en.html"))))
  (display res-body)
  (newline))

Above code display only false value, #f. After changing res-body
to res-headers, it display;
  #&amp;lt;&amp;lt;response&amp;gt; version: (1 . 1) code: 200 reason-phrase: "OK" headers:
((date . #&amp;lt;date nanosecond: 0 second: 42 minute: 50 hour: 7 day: 27 month:
4 year: 2012 zone-offset: 0&amp;gt;) (server . "Apache/2.2.14") (accept-ranges
bytes) (cache-control (max-age . 0)) (expires . #&amp;lt;date nanosecond: 0
second: 42 minute: 50 hour: 7 day: 27 month: 4 year: 2012 zone-offset: 0&amp;gt;)
(vary accept-encoding) (connection close) (transfer-encoding (chunked))
(content-type text/html) (content-language "en")) port: #&amp;lt;closed: file 0&amp;gt;&amp;gt;

Oh, Content-Length missing!! Apache server of www.gnu.org replied response
without Content-Length via home.en.html request. Is
Content-Length mandatory of response? If so, it would be Apache's fault.
But if not so, I think it's better modify read-response-body of (web
response) in Guile.

Thanks.
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-27T08:04:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9396">
    <title>crash in guile-sqlite3</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9396</link>
    <description>&lt;pre&gt;Hello,

Some time ago, I noticed that there is a nice-looking libsqlite3
wrapper for Guile available at [1]. I am now trying to use it, but the
short example program I wrote seems to cause guile to crash in certain
places where sqlite-finalize is called.

I tried to run guile in gdb to get a backtrace from the crash. The
segfault seems to be triggered inside libsqlite3 code, but I could not
really get much useful information from it. I am thus writing here to
ask if someone else has more insight on why this is happening and if
it could be resolved.

The test program that demostrates this behavior is available in [2]
and it is also attached to this message. On a 32-bit Exherbo
installation with guile-2.0.5 it reproducibly crashes into "Illegal
instruction" message, while in a 64-bit Fedora 16 installation that
has guile-2.0.2 added it produces a Segmentation fault. The program is
fairly short, which I hope might make it easier to track the problem
down.

Is guile-sqlite3 actually in such a shape that it might be useful for
curious testers?

Thanks,
&lt;/pre&gt;</description>
    <dc:creator>Joonas Sarajärvi</dc:creator>
    <dc:date>2012-04-26T18:51:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9394">
    <title>SRFI-64 module and SRFI-78 module -- archive file attached</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9394</link>
    <description>&lt;pre&gt;Hello,

I've attatched a file archiving modules of my recent version of SRFI-64
implementation and SRFI-78.

SRFI-64 is "A Scheme API for test suites."
SRFI-78 is "Lightweight testing."

If you want to test your code, there are 5 options; using SRFI-64, SRFI-78,
unit-test of guile-lib, lib of test-suite in Guile source archive or your
own test suite. Here is four examples:

;;; filename: srfi-64-example.scm
(use-modules (srfi srfi-64))
(test-begin "vec-test")
(define v (make-vector 5 99))
(test-assert (vector? v))
(test-eqv 99 (vector-ref v 2))
(vector-set! v 2 7)
(test-eqv 7 (vector-ref v 2))
(test-end "vec-test")

;;; filename: srfi-78-example.scm
(use-modules (srfi srfi-78))
(define v (make-vector 5 99))
(check (vector? v) =&amp;gt; #t)
(check (vector-ref v 2) =&amp;gt; 99)
(vector-set! v 2 7)
(check (vector-ref v 2) =&amp;gt; 7)

;;; filename: unit-test-example.scm
(use-modules (unit-test) (oop goops))
(define v (make-vector 5 99))
(define-class &amp;lt;vec-test&amp;gt; (&amp;lt;test-case&amp;gt;))
(define-method (test-vector? (self &amp;lt;vec-test&amp;gt;))
  (assert-true (vector? v)))
(define-method (test-99 (self &amp;lt;vec-test&amp;gt;))
  (assert-equal 99 (vector-ref v 2)))
(define-method (test-7 (self &amp;lt;vec-test&amp;gt;))
  (vector-set! v 2 7)
  (assert-equal 7 (vector-ref v 2)))
(exit-with-summary (run-all-defined-test-cases))

;;; filename: test-suite-example.scm
(use-modules (test-suite lib))
(define v (make-vector 5 99))
(pass-if "vector?" (vector? v))
(pass-if "99" (eqv? 99 (vector-ref v 2)))
(vector-set! v 2 7)
(pass-if "7" (eqv? 7 (vector-ref v 2)))
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-26T08:27:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9393">
    <title>A question about http-get of (web client)</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9393</link>
    <description>&lt;pre&gt;First, here is an example of http-get:

  (use-modules ((web uri)    #:select (string-&amp;gt;uri))
               ((web client) #:select (http-get)))
  (call-with-values (lambda ()
                      (http-get
                       (string-&amp;gt;uri "http://www.gnu.org/software/guile/")))
    (lambda (res-headers res-body)
      (display res-body)
      (newline)))

It works well. But after changing url string from "
http://www.gnu.org/software/guile/" to "http://www.gnu.org/", it did not
work. Last two lines of Backtrace is:
  web/http.scm:184:11: In procedure read-header:
  web/http.scm:184:11: Throw to key `bad-header' with args `(uri
"home.html")'.

I think http://www.gnu.org/ need to know browser's encoding language.
http-get accept extra-headers but I don't know how to fill the contents of
headers in web and scheme. In scheme, I think acon magic(?) is needed.
Please show me an example to fill headers. I want to fill browser's
encoding language, browser's type and some cookies. Oh, cookie would be
need if  http://www.google.com/ , I think, and would be got
from res-headers.
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-26T01:15:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9386">
    <title>read-header procedure of (web http) module has a bug?</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9386</link>
    <description>&lt;pre&gt;Hello,

I wonder I found a bug;
read-header procedure use parse-header procedure but parse-header is
defined after read-header!!
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-24T23:09:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9377">
    <title>Guile-PG 0.44 available</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9377</link>
    <description>&lt;pre&gt;release notes:

  Bug fix plus "make check" improvements.

  thi

README excerpt:

  Guile-PG is a collection of modules for Guile allowing access to
  the PostgreSQL RDBMS from Scheme programs.

  The low-level module ‘(database postgres)’ provides an almost
  one-to-one correspondence with the PostgreSQL "libpq" C library
  interface.  Other higher-level modules, typically named
  ‘(database postgres-FOO)’, provide abstractions and convenience
  procedures.

  This is alpha code (pre 1.0 release), tested with various, but
  not all, versions of Guile and PostgreSQL.  It may have bugs,
  and the interfaces may change from version to version.

NEWS excerpt:

  - 0.44 | 2012-04-20

    - distribution now .tar.xz

        If you have GNU tar, you can use "tar xf" and it will DTRT.
        If not, you can use "xz -dc TARBALL | tar xf -" to unpack.

    - bugfix: ‘pg-get-copy-data’ handles unspecified ‘async?’

        Previously, if ‘async?’ was unspecified, it was incorrectly
        interpreted as true (i.e., "not false").  Now, if unspecified,
        it is interpreted correctly as false.

    - testing slack for pre-8.1 ‘pg-client-encoding’

        Previously, the types-table test was too strict when checking
        the ‘pg-client-encoding’ return value, expecting "UTF-8" only.
        Now, it accepts also "UNICODE", which is the norm for PostgreSQL
        prior to 8.1.

    - support for ‘make check KEEPD=1’

        If you run "make check" many times, you can avoid daemon bounce
        overhead by specifying ‘KEEPD=1’, which inhibits daemon killing.

    - maintenance tools
      - GNU Autoconf 2.68
      - GNU Automake 1.11.5
      - GNU Libtool 2.4.2
      - Guile-BAUX 20120309.1509.1c4bb92
      - SNUGGLE 0.1

tarball and its detached signature in dir:

  http://download.savannah.gnu.org/releases/guile-pg/

homepage:

  http://www.nongnu.org/guile-pg/


&lt;/pre&gt;</description>
    <dc:creator>Thien-Thi Nguyen</dc:creator>
    <dc:date>2012-04-20T09:15:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9376">
    <title>Guile-PG 0.43 available</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9376</link>
    <description>&lt;pre&gt;release notes:

  Guile-PG ventures out of the 7-bit ghetto!
  (But venerates geezers PostgreSQL 7.4 and 8.0,
  fending off punkish Guile \x indignities, pfui!)

  Note that section 9.6 in the manual sez "[Guile] 2.0 doesn't have
  this problem", but that is not yet fully confirmed.  See the thread
  referenced in the footnote for the ongoing data-collection effort.

  thi

README excerpt:

  Guile-PG is a collection of modules for Guile allowing access to
  the PostgreSQL RDBMS from Scheme programs.

  The low-level module ‘(database postgres)’ provides an almost
  one-to-one correspondence with the PostgreSQL "libpq" C library
  interface.  Other higher-level modules, typically named
  ‘(database postgres-FOO)’, provide abstractions and convenience
  procedures.

  This is alpha code (pre 1.0 release), tested with various, but
  not all, versions of Guile and PostgreSQL.  It may have bugs,
  and the interfaces may change from version to version.

NEWS excerpt:

  - 0.43 | 2012-02-06

        [PBI] means "WARNING: potentially backward-incompatible".

    - bugfix: ‘sql-quote’ translates backslash (#\\) to ‘\134’

        Previously, backslash characters were passed through
        unmodified.  Now, they are translated to the string "\134"
        (i.e., the four characters ‘#\\’, ‘#\1’, ‘#\3’, ‘#\4’).

    - [PBI] ‘bytea’ stringifier outputs only one backslash

        If the ‘bytea’ stringifier from ‘(database postgres-types)’ is
        used standalone, this represents a BACKWARD INCOMPATIBLE change.
        In the normal case, however, where the stringifier is used in
        conjunction with ‘sql-quote’, this change is transparent.

    - new (database postgres-qcons) proc: string-xrep

        Some versions of Guile emit ‘\xXX’ to represent the octet with
        hex value XX when constructing the external representation of a
        string, for certain octets.  Furthermore, some versions of
        PostgreSQL cannot grok such escape sequences anyway.  The new
        procedure ‘string-xrep’ is like ‘object-&amp;gt;string’ (for a string
        arg) except that it explicitly emits the octet itself, except
        for ‘#\\’ and and ‘#\"’, which are backslash-escaped as normal.

    - ‘(database postgres-qcons) idquote’ no longer emits ‘\xXX’

        Before, ‘idquote’ used ‘object-&amp;gt;string’ internally, and thus
        suffered from the problems described in the preceding NEWS
        entry.  Now, it uses ‘string-xrep’.

    - ‘(database postgres-col-defs) validate-def’ more permissive

        A column name may now be any symbol that does not contain
        whitespace.  Previously it was restricted to a symbol whose
        constituent characters were alphanumeric or underscore.

        This change makes Guile-PG less strict (in some sense) than
        PostgreSQL, which imposes other rules.  Overarching is the
        recommendation from PostgreSQL to consistently use a "delimited
        identifier" (aka "quoted identifier") rather than a naked name.
        That's what ‘idquote’ and ‘string-xrep’, both used extensively
        in Guile-PG, do.  See section "Identifiers and Key Words" in
        chapter "SQL Syntax" in the PostgreSQL documentation, for more
        information.

    - ‘pgtable-manager’ and ‘pgtable-worker’ likewise relaxed

        These use ‘(database postgres-col-defs)’ procs and new proc
        ‘string-xrep’ internally, and thus benefit from the changes
        mentioned in the preceding NEWS entries.  Notably, table and
        column names are less constrained.  For example, see file
        test/types-table.scm, proc ‘test-m2’.

        [Probably "relaxed" is not as good as "strictness relaxed and
        multi-byte-fu enhanced", but that does not fit on one line.]

    - fake cluster created on-demand for "make check"

        In addition to a fake installation, "make check" now also
        creates a cluster under test/fake-cluster/ configured for
        Unix-domain connections, and kicks/kills the daemon around the
        actual ‘runtest TEST’ invocations.  This means it is no longer
        necessary to set env var ‘PGDATABASE’.  In fact, that and env
        var ‘PGHOST’ are now silently ignored, since ‘runtest’ clobbers
        them internally.

        If you previously tested Guile-PG against different PostgreSQL
        versions by varying ‘PGDATABASE’, you now need to vary env var
        ‘INITDB’ instead, and zonk the cluster before the "make check"
        invocation.  Something like:

          $(MAKE) delete-cluster
          $(MAKE) check DEBUG=1 INITDB=/a/particular/initdb

        in directory test/ would be fine.  See README section "Testing".

tarball and its detached signature in dir:

  http://download.savannah.gnu.org/releases/guile-pg/

homepage:

  http://www.nongnu.org/guile-pg/


&lt;/pre&gt;</description>
    <dc:creator>Thien-Thi Nguyen</dc:creator>
    <dc:date>2012-04-20T09:14:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9373">
    <title>http-post</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9373</link>
    <description>&lt;pre&gt;From the guile reference manual, web section:

"More helper procedures for the other common HTTP verbs would be a
good addition to this module.  Send your code to &amp;lt;guile-user&amp;lt; at &amp;gt;gnu.org&amp;gt;."

So, I say to guile-user, "here is my code".

This http-post implementation takes the request body as either a
bytevector or as a string, in which case it first converts it to a
bytevector either using a default encoding (currently always utf-8,
but perhaps should be snarfed from the current locale) or using a
caller-requested encoding (currently only utf-8 is accepted, though).

I think the next steps after this patch are to:
- be able to work with a greater variety of encodings;
- since form data of the type "key1=value1&amp;amp;key2=value2..." is so
common in POST bodies, accept post data as key-value pairs represented
by an alist (which would be coerced into a bytevector automatically).

&lt;/pre&gt;</description>
    <dc:creator>gregory benison</dc:creator>
    <dc:date>2012-04-17T03:34:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9371">
    <title>ETRACK 0.9915 available</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9371</link>
    <description>&lt;pre&gt;release notes:

  Rolling, rolling...

  thi

README excerpt:

  This directory contains ETRACK, a simple package to track
  expenses: query, add, delete, update.  You can use ETRACK
  from Emacs or from the command-line.

NEWS excerpt:

  - 0.9915 | 2012-04-15
    - maintenance release: don't require Guile 1.4.x

tarball, prettified code, etc, in dir:

  http://www.gnuvola.org/software/etrack/

patronage:

  http://www.gnuvola.org/patronage.html


&lt;/pre&gt;</description>
    <dc:creator>Thien-Thi Nguyen</dc:creator>
    <dc:date>2012-04-15T14:40:14</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9367">
    <title>SRFI-64 implementation for Guile 2.0</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9367</link>
    <description>&lt;pre&gt;Hello, world! :)

I'm a newbie of scheme. I'd heard the testing framework SRFI-64 but failed
to use it on Guile 2.0.
After attempt to solve this problem, I made a guile module to pass the test
suite for SRFI-64 by Donovan Kolbly.

--
1. srfi/srfi-64.scm is a SRFI-64 implementation for Guile 2.0.
   srfi-64-test.scm is a test suite for SRFI-64 itself by Donovan Kolbly.

   $ ls -RF
   .:
   README  srfi/  srfi-64-test.scm
   ./srfi:
   srfi-64.scm
   $

2. srfi/srfi-64.scm provide the srfi-64 module for Guile.

   $ guile -L . --use-srfi=64 srfi-64-test.scm
   %%%% Starting test SRFI 64 - Meta-Test Suite  (Writing full log to "SRFI
64 - Meta-Test Suite.log")
   # of expected passes      51
   # of expected failures    2
   $ ls -F
   README  SRFI 64 - Meta-Test Suite.log  srfi/  srfi-64-test.scm
   $

3. Somethings were changed:
   1) test-log-to-file is a parameter object.
   2) test-on-test-end-simple and test-on-final-simple have a return value.
   3) and so on.

   Example of log to another file:

   $ guile -L `pwd`
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (use-modules (srfi srfi-64))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-log-to-file (open-output-file "my-log.log"))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (load "srfi-64-test.scm")
   %%%% Starting test SRFI 64 - Meta-Test Suite
   # of expected passes      51
   # of expected failures    2
   $1 = (51 2 0 0 0)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (close-output-port (test-log-to-file))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; ,q
   $

   Contents of log files are same:

   $ ls -F
   README  SRFI 64 - Meta-Test Suite.log  my-log.log  srfi/
 srfi-64-test.scm
   $ diff SRFI\ 64\ -\ Meta-Test\ Suite.log my-log.log
   $ rm SRFI\ 64\ -\ Meta-Test\ Suite.log my-log.log
   $ ls -F
   README  srfi/  srfi-64-test.scm
   $

   Example of not log:

   $ guile -L `pwd`
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (use-modules (srfi srfi-64))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-log-to-file #f)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (load "srfi-64-test.scm")
   %%%% Starting test SRFI 64 - Meta-Test Suite
   # of expected passes      51
   # of expected failures    2
   $1 = (51 2 0 0 0)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; ,q
   $

   The log file were not generated:

   $ ls -F
   README  srfi/  srfi-64-test.scm
   $

   Example in Guile interactive mode:

   $ guile -L `pwd`
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (use-modules (srfi srfi-64))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-log-to-file #f)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-begin "vec-test")
   %%%% Starting test vec-test
   $1 = ("vec-test")
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (define v (make-vector 5 99))
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-assert (vector? v))
   $2 = pass
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-eqv 99 (vector-ref v 2))
   $3 = pass
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (vector-set! v 2 7)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-eqv 7 (vector-ref v 2))
   $4 = pass
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-eqv 8 (vector-ref v 2))
   $5 = fail
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; (test-end "vec-test")
   # of expected passes      3
   # of unexpected failures  1
   $6 = (3 0 0 1 0)
   scheme&amp;lt; at &amp;gt;(guile-user)&amp;gt; ,q
   $
&lt;/pre&gt;</description>
    <dc:creator>Sunjoong Lee</dc:creator>
    <dc:date>2012-04-12T21:53:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.lisp.guile.user/9364">
    <title>Guile-SNMP 0.2.3</title>
    <link>http://comments.gmane.org/gmane.lisp.guile.user/9364</link>
    <description>&lt;pre&gt;Hi All,

  I've just released guile-snmp-0.2.3 on github. I've included the
NEWS below and in addition to that there's also SNMPv3 support,
support for async calls (which in turns means you can use it as a trap
reciever). expanded use of goops generics for access to wrapped types,
and support for snmp getbuilk. There's also an included spec file that
now only gets 1 warning on rpmlint, though I've not tested the
resulting packages yet.

  I'm going to work on a bit of syntactic sugar for creating agents,
and direct use of SMI textual conventions (octet-str display hints are
working but aren't used by default as it'll break the API).

Changes in guile-snmp-0.2.3 (since guile-snmp-0.2.2)

* MIB browsing: You can now use goops' describe function to get
  information about a MIB module, or an oid e.g.:

  (use-mibs BRIDGE-MIB)
          (describe BRIDGE-MIB)
          (describe dot1dStpRootPort)

        * (snmp display-hint) provides apply-octet-str-display-hint to
  value-bytes to a string using the relevant display hint. This
  will be automated in future

* Basic agent support: The net-snmp agent handler infrastructure
  for scalars and tables are now wrapped. This work as stand alone
  and AgentX

* Agents sysORTable registration via (un)register-sysor-table

* Some fixes to ASN-TYPE handling around signedness

* Fixes to setting/serving of ASN-OBJECT-ID varbinds

* Support ASN-FLOAT and ASN-DOUBLE

* Some more OID related routines:

  oid? predicate
  oid-length retrieves length of an oid
  (/ oid1 oid2) is oid2 a prefix of oid1

* Various bug fixes for automated oid resolution



&lt;/pre&gt;</description>
    <dc:creator>Tristan Colgate</dc:creator>
    <dc:date>2012-04-03T11:03:43</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.lisp.guile.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.lisp.guile.user</link>
  </textinput>
</rdf:RDF>

