[Chicken-users] wish-list

2010-10-25 Thread Felix

I added a wish-list to the wiki to hold stuff that would be nice to
have. This is of course not meant as a replacement for the
bug-tracker, but it may be worthwhile to have a place where to put
more ambitious ideas.

  http://wiki.call-cc.org/wish-list

cheers,
felix

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] wish-list

2010-10-25 Thread Peter Bex
On Mon, Oct 25, 2010 at 06:07:06AM -0400, Felix wrote:
 
 I added a wish-list to the wiki to hold stuff that would be nice to
 have. This is of course not meant as a replacement for the
 bug-tracker, but it may be worthwhile to have a place where to put
 more ambitious ideas.
 
   http://wiki.call-cc.org/wish-list

I love it!

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music.
-- Donald Knuth

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] wish-list

2010-10-25 Thread Christian Kellermann
* Peter Bex peter@xs4all.nl [101025 12:12]:
 On Mon, Oct 25, 2010 at 06:07:06AM -0400, Felix wrote:
  
  I added a wish-list to the wiki to hold stuff that would be nice to
  have. This is of course not meant as a replacement for the
  bug-tracker, but it may be worthwhile to have a place where to put
  more ambitious ideas.
  
http://wiki.call-cc.org/wish-list
 
 I love it!

I want a pony too!

Christian

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


[Chicken-users] Survey results

2010-10-25 Thread Christian Kellermann
Dear Chicken Fans!

Thank you very much for all your replies during the last week(s).
I have updated the portability page accordingly. If you miss your
operating system in there or are running a newer version or what
not please don't be afraid to change it. It's a wiki and you don't
need to authenticate to change it.

The url is http://wiki.call-cc.org/portability

I have received a total of 30 reported chicken installs in use:

| # Users | Operating System |
|-+--|
|   1 | FreeBSD  |
|   1 | Haiku|
|  13 | Linux|
|   6 | Mac OS X |
|   1 | NetBSD   |
|   4 | OpenBSD  |
|   2 | Windows/mingw|
|   2 | Windows/cygwin   |

| # Users | Architecture |
|-+--|
|   1 | MIPS |
|   4 | PPC  |
|  19 | x86  |
|   6 | x64  |

| # Users | Chicken Version |
|-+-|
|   3 |   4.6.3 |
|   5 |   4.6.2 |
|   1 |   4.6.1 |
|  14 |   4.6.0 |
|   1 |   4.5.7 |
|   5 |   4.5.0 |
|   1 |   4.2.0 |

Now let's hear some speculations on what this all means. I would
also love to hear from some peculiar hardware you are running chicken
on. I know some of you do.

Kind regards,

Christian

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Survey results

2010-10-25 Thread Alan Post
On Mon, Oct 25, 2010 at 12:48:22PM +0200, Christian Kellermann wrote:
 Dear Chicken Fans!
 
 Thank you very much for all your replies during the last week(s).
 I have updated the portability page accordingly. If you miss your
 operating system in there or are running a newer version or what
 not please don't be afraid to change it. It's a wiki and you don't
 need to authenticate to change it.
 
 The url is http://wiki.call-cc.org/portability
 
 I have received a total of 30 reported chicken installs in use:
 
 | # Users | Operating System |
 |-+--|
 |   1 | FreeBSD  |
 |   1 | Haiku|
 |  13 | Linux|
 |   6 | Mac OS X |
 |   1 | NetBSD   |
 |   4 | OpenBSD  |
 |   2 | Windows/mingw|
 |   2 | Windows/cygwin   |
 
 | # Users | Architecture |
 |-+--|
 |   1 | MIPS |
 |   4 | PPC  |
 |  19 | x86  |
 |   6 | x64  |
 
 | # Users | Chicken Version |
 |-+-|
 |   3 |   4.6.3 |
 |   5 |   4.6.2 |
 |   1 |   4.6.1 |
 |  14 |   4.6.0 |
 |   1 |   4.5.7 |
 |   5 |   4.5.0 |
 |   1 |   4.2.0 |
 
 Now let's hear some speculations on what this all means. I would
 also love to hear from some peculiar hardware you are running chicken
 on. I know some of you do.
 
 Kind regards,
 
 Christian
 

I'm personally surprised to see 10% of users running OpenBSD, with
*BSD combined coming in at 30% of usage.  I would have guessed that
number to be lower. We have some critical users, namely our single
MIPS person and the lone FreeBSD, Haiku, and NetBSD people.

The cross product of the operating system and cpu architecture usage
suggests we don't really test enough combinations of os and cpu.
It's too bad there isn't any ARM platform use.

Have any of you other OpenBSD users patched your linker to avoid
spurious warnings of strcat, c when you link chicken?  

-Alan
-- 
.i ko djuno fi le do sevzi

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Survey results

2010-10-25 Thread Peter Bex
On Mon, Oct 25, 2010 at 07:05:36AM -0600, Alan Post wrote:
 The cross product of the operating system and cpu architecture usage
 suggests we don't really test enough combinations of os and cpu.

It's true, for haiku, Windows and solaris, and some architectures.

I myself use it on NetBSD on both amd64(x86_64) and macppc, and
I know that Alaric uses it on NetBSD as well (the lone NetBSD
user in Christian's results is someone else), so we have more
NetBSD users than the poll results suggest.

I expect the same to be true for the other platforms.

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music.
-- Donald Knuth

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Survey results

2010-10-25 Thread Shawn Rutledge
Oops I wasn't paying attention and missed the survey.  I run chicken
most often on Linux, 64-bit, looks like I have 4.5.0 at the moment.
Also have 4.5.0 on MacOS.  I was using chicken on OpenMoko (an ARM
platform, really nobody else is running on arm?) and on a Zaurus
before that, but that was version 3... I don't think I got around to
trying 4 yet, and haven't been doing anything there for a couple years
anyway.  And I have tried it on Windows XP at some point, but not
recently.

On Mon, Oct 25, 2010 at 3:48 AM, Christian Kellermann
ck...@pestilenz.org wrote:
 Dear Chicken Fans!

 Thank you very much for all your replies during the last week(s).
 I have updated the portability page accordingly. If you miss your
 operating system in there or are running a newer version or what
 not please don't be afraid to change it. It's a wiki and you don't
 need to authenticate to change it.

 The url is http://wiki.call-cc.org/portability

 I have received a total of 30 reported chicken installs in use:

 | # Users | Operating System |
 |-+--|
 |       1 | FreeBSD          |
 |       1 | Haiku            |
 |      13 | Linux            |
 |       6 | Mac OS X         |
 |       1 | NetBSD           |
 |       4 | OpenBSD          |
 |       2 | Windows/mingw    |
 |       2 | Windows/cygwin   |

 | # Users | Architecture |
 |-+--|
 |       1 | MIPS         |
 |       4 | PPC          |
 |      19 | x86          |
 |       6 | x64          |

 | # Users | Chicken Version |
 |-+-|
 |       3 |           4.6.3 |
 |       5 |           4.6.2 |
 |       1 |           4.6.1 |
 |      14 |           4.6.0 |
 |       1 |           4.5.7 |
 |       5 |           4.5.0 |
 |       1 |           4.2.0 |

 Now let's hear some speculations on what this all means. I would
 also love to hear from some peculiar hardware you are running chicken
 on. I know some of you do.

 Kind regards,

 Christian

 ___
 Chicken-users mailing list
 Chicken-users@nongnu.org
 http://lists.nongnu.org/mailman/listinfo/chicken-users


___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


[Chicken-users] Procedures in the `read' series shadowed by GNU readline

2010-10-25 Thread Yi DAI
Hi,


I just found that procedures in the `read' series, like `read', `read-line',
etc do not work in the interactive repl if I make use of the GNU readline
egg. When I try to `(read)', it does not wait for my input any more instead
directly jump to a new prompt as if I enter nothing.  Below is my .csirc

(use readline regex datatype matchable)

(current-input-port (make-gnu-readline-port))

(gnu-history-install-file-manager
  (string-append (or (getenv HOME) .) /.csi.history))

But if I do not use readline (also comment the last two line of gnu-stuff),
it works fine. I am currently using 4.6.0 on Archlinux.


Best regards,


-- 
DAI Yi
(代 毅)
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Procedures in the `read' series shadowed by GNU readline

2010-10-25 Thread Mario Domenech Goulart
Hi

On Mon, 25 Oct 2010 21:46:28 +0200 Yi DAI plm@gmail.com wrote:

 I just found that procedures in the `read' series, like `read', `read-line',
 etc do not work in the interactive repl if I make use of the GNU readline egg.
 When I try to `(read)', it does not wait for my input any more instead 
 directly
 jump to a new prompt as if I enter nothing.  Below is my .csirc

 (use readline regex datatype matchable)

 (current-input-port (make-gnu-readline-port))

 (gnu-history-install-file-manager
   (string-append (or (getenv HOME) .) /.csi.history))

 But if I do not use readline (also comment the last two line of gnu-stuff), it
 works fine. I am currently using 4.6.0 on Archlinux.

You can use a dirty trick: in your .csirc, save your default stdin
before setting it to `(make-gnu-readline-port)'. When you want the old
`(current-input-port)', just parameterize it using the value you saved.

So, your .csirc would be:

(use readline regex datatype matchable)

(define old-stdin (current-input-port))

(current-input-port (make-gnu-readline-port))

(gnu-history-install-file-manager
  (string-append (or (getenv HOME) .) /.csi.history))


When you want to use, say, `read' without the readline port, do:

  (parameterize ((current-input-port old-stdin)) (read))

Best wishes.
Mario
-- 
http://parenteses.org/mario

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


[Chicken-users] Chicken Gazette - Issue 9

2010-10-25 Thread Jim Ursetto
 _/_/_/  _/_/_/ /
  _/_/_/_/  _/_/_/  _/  _/  _/_/_/_/_/ /
 _/_/_/  _/  _/_/_/  _/_/_/_/  _/_/   /
_/_/_/  _/  _/_/  _/_/_/_/   /
 _/_/_/  _/_/  _/_/_/_/  _/_/_/_/_/  _/_/   .

--[ Issue 9 ]-- G A Z E T T E
   brought to you by the Chicken Team


== 0. Introduction

Welcome to issue 9 of the Chicken Gazette, brought to you by the
letter `k` and the procedure `call/cc`.

== 1. The Hatching Farm

First off, this week's egg news.

  * http-session (http://wiki.call-cc.org/egg/http-session): fix a
bug in session ID generation for long-lived processes, due to a
timer overflow in `current-milliseconds`;
  * estraier (http://wiki.call-cc.org/egg/estraier-client):
performance improvement and regex dependency dropped;
  * wiki-parse (http://wiki.call-cc.org/egg/wiki-parse): deleted,
as it was unused and had diverged too far from upstream to be
maintained;
  * chickadee (http://wiki.call-cc.org/egg/chickadee): added a
wrapper program which simplifies installing and running a server;
  * shell (http://wiki.call-cc.org/egg/shell): a thin wrapper around
a turtle;
  * salmonella (http://wiki.call-cc.org/egg/salmonella): now checks
that eggs are documented and executes egg tests; also something
you can find on a turtle

To take advantage of the new salmonella egg testing, a proper exit
code was added to `tests/run.scm` in many eggs, reflecting whether a
test failure occurred.

Additionally, explicit dependencies on the new `regex` egg were added
to yet more eggs for compatibility with 4.6.2 and later.

And now a public service announcement. Egg authors, now hear this.
When your egg installs both library files via `install-extension` and
also an executable via `install-program`, you need to use different
IDs for each. By convention, the library files should use the name
of the egg (such as `chicken-doc`) and the executable should use this
same name with something appended, such as `chicken-doc-cmd`. This
prevents the uninstaller from losing track of files. Specifically,
the .setup-info files created by `chicken-install` to track extension
metadata will clobber each other if the IDs are identical.

== 2. Yolklore

Chicken core development was relatively active this week. Dare I say
excitingly so? Yes, I dare it.

Peter Bex committed a patch to the irregex-bugfixes branch that fixes
ticket 411 (https://bugs.call-cc.org/ticket/411), correcting an issue
introduced in 4.6.2.  It makes submatch accessors return `#f` instead
of throwing an error when the submatch is in range but non-matching.
For example, this no longer errors out:

  (string-search-positions (foo)|(bar)|(baz) bar)
  ;= ((0 3) (#f #f) (0 3) (#f #f))

The new blob literal syntax mentioned in the last issue was changed
from #{HEX ...} to #${HEX ...} after concerns were voiced about the
loss of valuable ASCII real-estate. The use of $ to mean hex is of
course well-known to assembly-language programmers of a certain age.

`integer64` and `unsigned-integer64` are now supported as FFI
return values, including in `let-location`, fixing ticket 413
(https://bugs.call-cc.org/ticket/413).

When fed a non-link argument, `read-symbolic-link` in `Unit posix`
now returns that argument when told to resolve symlinks recursively.
Previously it threw an error.

`delete-directory` in `Unit posix` now accepts an optional argument
telling it to delete recursively.

Optional per-slot SRFI-17 setters have been added to `define-record`.

And there were a few `types.db` fixes, as occur from time to time.
`types.db` is a database of procedure signatures for the core, and
is used by the scrutinizer to check procedure argument types at
compile-time.

== 3. Chicken Talk

In which I summarize our last week of mail.

Enwin Thun wrote in
(http://www.mail-archive.com/chicken-users@nongnu.org/msg12297.html)
with a problem installing eggs after upgrading to Ubuntu Maverick.
The cause is that the Chicken infrastructure migrated to new
servers between 4.5.0 and 4.6.0, but Maverick is still on 4.5.0
which points to the old servers. The solution is to provide the
`-l` option to `chicken-install` to override the remote repository
location or, preferably, to change its configuration file.
The changes are detailed at the infrastructure migration page
(http://wiki.call-cc.org/infrastructure-migration).

Discussion is ongoing about the proper procedure to install datafiles
(http://www.mail-archive.com/chicken-users@nongnu.org/msg12208.html)
for eggs, as well as the proper place for compliance with the
Filesystem Hierarchy Standard and BSD's hier(7).  The only eggs known
to the author to be affected are slatex, chicken-doc, and chickadee,
but egg authors are advised to keep an eye on this breaking issue.

On a related note, Kon Lovett recommended 

Re: [Chicken-users] Chicken Gazette - Issue 9

2010-10-25 Thread Alan Post
On Mon, Oct 25, 2010 at 05:31:49PM -0500, Jim Ursetto wrote:
  Install
 
 First, install chicken-doc.
 
   $ chicken-install -s chicken-doc
 
 The nicest way to work with chicken-doc is to check out a copy of
 the wiki from Subversion, then use chicken-doc-admin to prepare it
 for use. But the quickest way to get started is to download today's
 pre-baked chicken-doc repository, a 1.4MB gzipped tarball:
 
   $ cd `csi -p '(chicken-home)'` 
 curl http://3e8.org/pub/chicken-doc/chicken-doc-repo.tgz |
 sudo tar zx
 
 The repository goes inside your Chicken install directory and you may
 need sudo to write to it. Alternatively, you could put the repository
 anywhere you want like this:
 
   export CHICKEN_DOC_REPOSITORY=/path/to/my/cdoc/repo/dir
 

I already have a copy of the wiki checked out.  I have installed
chicke-doc, but I have no chicken-doc-admin command.  How
chicken-doc-admin is used, over even where you get it is a bit
glossed over here.

How do I prepare my already checked out repository for use by
chicken-doc?

-Alan
-- 
.i ko djuno fi le do sevzi

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Chicken Gazette - Issue 9

2010-10-25 Thread Alan Post
On Mon, Oct 25, 2010 at 05:31:49PM -0500, Jim Ursetto wrote:
  chicken-doc-admin
 
 So this is the way to use chicken-doc as nature intended: checkout
 the wiki and then process it with chicken-doc-admin. First, grab a
 copy of the wiki and initialize an empty chicken-doc repository:
 
   $ chicken-install -s chicken-doc-admin
   $ sudo chicken-doc-admin -i
   $ svn co --username anonymous --password  \
   http://code.call-cc.org/svn/chicken-eggs/wiki
 
 Then add the Chicken 4 man and egg pages to your database:
 
   $ sudo chicken-doc-admin -m wiki/man/4
   49 man pages processed, 49 updated
   $ sudo chicken-doc-admin -e wiki/eggref/4
   347 eggs processed, 347 updated
 

I run this command and get an error message:

  $ sudo chicken-doc-admin -m man/4 

  Error: (irregex-match-start-index) not a valid index
  #regexp-match (8 submatches)
  8

Call history:

-string  
ensure-string1437 
-string  
setup-api#user-install-setup  
tcp-connect-timeout   
tcp-read-timeout  
tcp-write-timeout 
chicken-version   
conc  
make-parameter  --

I'll be happy to help debug, if someone wants to work with me over
e-mail or IRC.  Or you can just tell me what I'd doing wrong!

-Alan
-- 
.i ko djuno fi le do sevzi

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Chicken Gazette - Issue 9

2010-10-25 Thread Alan Post
On Mon, Oct 25, 2010 at 05:31:49PM -0500, Jim Ursetto wrote:

  chicken-doc-admin
 
 So this is the way to use chicken-doc as nature intended: checkout
 the wiki and then process it with chicken-doc-admin. First, grab a
 copy of the wiki and initialize an empty chicken-doc repository:
 
   $ chicken-install -s chicken-doc-admin
   $ sudo chicken-doc-admin -i
   $ svn co --username anonymous --password  \
   http://code.call-cc.org/svn/chicken-eggs/wiki
 
 Then add the Chicken 4 man and egg pages to your database:
 
   $ sudo chicken-doc-admin -m wiki/man/4
   49 man pages processed, 49 updated
   $ sudo chicken-doc-admin -e wiki/eggref/4
   347 eggs processed, 347 updated
 
 Now you can use chicken-doc as before. Later, you can update your
 checkout and rerun the processor:
 
   $ svn up wiki/eggref/4
   $ sudo chicken-doc-admin -e wiki/eggref/4
   347 eggs processed, 28 updated
 
 chicken-doc-admin updates only the nodes that have changed since last
 run. So if you make some local changes, you can easily preview them
 without checking in:
 
   $ emacs wiki/eggref/4/atom
   $ sudo chicken-doc-admin -e wiki/eggref/4
   347 eggs processed, 1 updated
 
 chicken-doc-admin has more options than you could possibly dream
 of (as long as you can count no higher than ten); check out the
 documentation (http://3e8.org/chickadee/chicken-doc-admin) for
 details.
 

Hey look, I can keep reading and all my questions are answered!

-Alan
-- 
.i ko djuno fi le do sevzi

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] Chicken Gazette - Issue 9

2010-10-25 Thread Jim Ursetto
Hi Alan.

On Mon, Oct 25, 2010 at 18:06, Alan Post alanp...@sunflowerriver.org wrote:
  $ sudo chicken-doc-admin -m man/4

  Error: (irregex-match-start-index) not a valid index
  #regexp-match (8 submatches)
  8

It's a problem with irregex in 4.6.2 (the one that was fixed by
Peter).  You have to pull the irregex-bugfixes branch or downgrade to
4.6.1 or earlier.

Jim

___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users