An unlimited stack from ulimit crashes guile

2019-05-22 Thread Sven Hartrumpf
Hi. For some programs, I need an unlimited stack, i.e. ulimit -S -s unlimited is in effect. (Yes, I know this might be dangerous, but I have no workaround, yet.) guile does not like this, for example the version 2.2.4 packaged with Ubuntu 19.04. Also when building a local version from the 2.2.4 t

Re: propagating a coding setting across source files

2012-01-11 Thread Sven Hartrumpf
Hi Andy. Mon, 09 Jan 2012 23:51:42 +0100, wingo wrote: >> I added to the master file the following comment: >> >> ; coding: iso-8859-1 >> >> which works as documented. >> How can I avoid to add this comment line to all the other files >> which are currently included by the master file using "load"

Re: propagating a coding setting across source files

2011-12-02 Thread Sven Hartrumpf
Fri, 2 Dec 2011 04:55:39 -0800 (PST), spk121 wrote: > I'm pretty sure that, for 2.0.x at least, if you don't > specify an encoding, it presumes iso-8859-1 as the default. Not when loading a file with Latin-1 characters: > cat aa.scm (define c #\ä) > guile GNU Guile 2.0.3 ... scheme@(guile-user)>

propagating a coding setting across source files

2011-12-02 Thread Sven Hartrumpf
Hi all. After a long period of working with other Schemes, I am returning to guile for some tests to see what Guile has achieved in recent years. My test program is made up of around 100 scheme files, all encoded in latin-1. I added to the master file the following comment: ; coding: iso-8859-1

iota from SRFI-1

2006-10-11 Thread Sven . Hartrumpf
Hi all. How can I use the iota function from SRFI-1? > rlwrap guile181 --use-srfi=1 guile> (iota 3 1) Backtrace: In standard input: 1: 0* [iota 3 1] standard input:1:1: In procedure iota in expression (iota 3 1): standard input:1:1: Wrong number of arguments to # ABORT: (wrong-number-of-args)