bug#13088: stack overflow while compiling

[Andy Wingo]

On Sat 08 Dec 2012 22:44, Stefan Israelsson Tampe  
writes:

> tail-call 2000+ argument function which is not supported in guile :-)

This should be supported.  Just fixed this in stable-2.0.

> I suggest that we close this bug or perhaps add a feature request for
> growing stacks.
>
> An alternate feature request is to have some way to tell guile the size
> of the stack at start up.

In this case I agree, there is no bug in the expander or in the
compiler.  We should be able to grow stacks, but that is tricky with
stable-2.0.  Ideally we would be able to link different stack segments
together with overflow/underflow handlers, as in the Dybvig paper, but
that would require some experimentation that would best be done on
master.

I pushed a patch based on yours to add a GUILE_STACK_SIZE environment
variable.  I hate environment variables but hopefully we can remove it
in 2.2.

Thanks for looking into this!

Andy
-- 
http://wingolog.org/

bug#12887: Broken pipe while generating guile-procedures.texi

[Andy Wingo]

On Tue 05 Mar 2013 21:49, l...@gnu.org (Ludovic Courtès) writes:

> ‘GUILE_INSTALL_LOCALE’?
>
>> Or should we go ahead and document it, and simply have its default value
>> change between 2.0 and 2.2?
>
> Yes, even better, since the setlocale change will have to be documented
> at least in NEWS anyway.
>
> Are you willing to look into it?

Sure.  I have some local patches that I will push when I next get a net
connection.

Cheers,

Andy
-- 
http://wingolog.org/

bug#13088: stack overflow while compiling

[Andy Wingo]

Marking as done.
-- 
http://wingolog.org/

bug#13076: guile: ",option prompt VALUE" only accepts literals

[Andy Wingo]

On Tue 04 Dec 2012 04:29, Daniel Hartwig  writes:

> The REPL prompt option accepts #f, strings, thunks, and procedures of
> one argument.  However, only the first two can be set using the
> meta-command ,option; one must use repl-option-set! for thunks and
> procedures.
>
> It seems that VALUE is not evaluated.

Fixed, thanks for the report.  Now it will always evaluate the RHS.

Note that this changes the behavior of ,on-error and ,compile-options,
but since they are interactive commands, that should be fine.

Andy
-- 
http://wingolog.org/

bug#12892: ‘gc-stats’ w/o ‘bytes-malloced’

[Andy Wingo]

On Thu 07 Mar 2013 13:29, Thien-Thi Nguyen  writes:

> What is harsh, however, is the constant rejection by debbugs of my mail:
> .
> Am i missing something?

I have no earthly idea why this is happening; it's certainly not
intentional.  Try mailing help-debb...@gnu.org to get folks to grep the
logs?  If that ML is itself managed by debbugs, you could mail someone
directly I guess -- Jim Meyering perhaps?  Dunno.

Andy
-- 
http://wingolog.org/

bug#13076: guile: ",option prompt VALUE" only accepts literals

[Andy Wingo]

And marking as done
-- 
http://wingolog.org/

bug#12892: ‘gc-stats’ w/o ‘bytes-malloced’

[Thien-Thi Nguyen]

() Andy Wingo 
() Thu, 07 Mar 2013 20:21:53 +0100

   [...] Dunno.

As an experiment, i've changed the cc to bug-guile in this response.
Maybe that will work.  Anyway, i'll followup w/ the debbugs folks.

-- 
Thien-Thi Nguyen
GPG key: 4C807502

bug#11887: [PATCH] Improve standards conformance of string->number (was Re: bug#11887: string->number edge cases)

[Mark H Weaver]

I wrote:
> Here's a patch to fix these problems.  Comments and suggestions welcome.

I went ahead and pushed this to stable-2.0.  I'm closing this bug.

Thanks,
  Mark

bug#12216: peek-char incorrectly *CONSUMES* eof

[Andy Wingo]

On Tue 05 Mar 2013 20:17, "David A. Wheeler"  writes:

> I reported:
>> > Guile's peek-char has a bug; it incorrectly *consumes* eof instead of
>> > just reporting it.
>
> Andy Wingo replied:
>> I have the feeling that for interactive use, if you expect to read a EOF
>> from a port and then continue, you have to not use peek-char.  You need
>> to handle your own lookahead buffer.  I know it's not a great answer,
>> but I can't think of anything else that makes sense.
>
> We don't want to read an EOF and then continue.
> We peek-char to not *CONSUME* an interactive EOF.

I understand what it is you want.  But I don't know of any sane way to
implement it.

Given that it is an edge case -- peek-char on an interactive port -- I
think the thing to do is to document this inconsistency, and for you (in
your code) to implement some sort of abstraction that does not use
peek-char.

That is to say, use read-char, and do unread-char as necessary.  Or keep
your own buffer around.

I know it isn't nice, but I don't know how to do anything better.

Andy
-- 
http://wingolog.org/

bug#13865: redefinition of +

[Andy Wingo]

On Mon 04 Mar 2013 15:24, Ian Price  writes:

> Er, screw the repl, but it happens in a script as well.
>
> (define (foo) (+ 1 1))
> (define (+ a b) (- a b))
> (display (foo))
> (display (+ 1 1))
> (newline)
>
> $ guile -s /tmp/file1.scm
> ;;; note: source file /tmp/file1.scm
> ;;;   newer than compiled 
> /home/ian/.cache/guile/ccache/2.2-LE-4-3.1/tmp/file1.scm.go
> ;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
> ;;;   or pass the --no-auto-compile argument to disable.
> ;;; compiling /tmp/file1.scm
> ;;; compiled /home/ian/.cache/guile/ccache/2.2-LE-4-3.1/tmp/file1.scm.go
> 22

I see you are on master.  Is this a problem only in master?

$ ~/src/guile-master/meta/guile /tmp/foo.scm 
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;   or pass the --no-auto-compile argument to disable.
;;; compiling /tmp/foo.scm
;;; compiled 
/home/wingo/src/guile-master/cache/guile/ccache/2.2-LE-8-3.1/tmp/foo.scm.go
22
$ ~/src/guile/meta/guile /tmp/foo.scm 
;;; note: auto-compilation is enabled, set GUILE_AUTO_COMPILE=0
;;;   or pass the --no-auto-compile argument to disable.
;;; compiling /tmp/foo.scm
;;; compiled 
/home/wingo/src/guile/cache/guile/ccache/2.0-LE-8-2.0/tmp/foo.scm.go
00

Andy
-- 
http://wingolog.org/

bug#12432: Dead links on projects page

[Andy Wingo]

On Thu 13 Sep 2012 11:47, Mark Skilbeck  writes:

> The following projects have dead links on the guile website:
>   GnuTLS,

This one seems fine, no?

>   BOKIN.

Removed, as it seems to have been removed upstream.

Thanks,

Andy
-- 
http://wingolog.org/

bug#13176: SRFI-37 does not terminate

[Andy Wingo]

On Thu 13 Dec 2012 22:45, l...@gnu.org (Ludovic Courtès) writes:

> The following case does not terminate:
>
> scheme@(guile-user)> (use-modules (srfi srfi-37))
> scheme@(guile-user)> (define opts (list (option '(#\I) #f #t (lambda _ #t
> scheme@(guile-user)> (args-fold '("-I") opts (lambda _ (error 
> "unrecognized")) (lambda _ #f) '())
> [spins forever]
>
> (This is an option with a short name, optional argument; it is used
> without that optional argument.)

As an args-fold user, you would be ideal to look into this one :-)

A
-- 
http://wingolog.org/

bug#13416: guile e0c211b segfaults when linked against libgc 7.1

[Andy Wingo]

On Sat 12 Jan 2013 03:22, Ben Noordhuis  writes:

> gc.c:212:1: warning: 'GC_get_free_space_divisor' defined but not used

This comes (I think) from configuring Guile against one version of
libgc, then upgrading or downgrading libgc, and then running "make"
without reconfiguring.

Closing as not a bug.

Andy
-- 
http://wingolog.org/

bug#13485: wrong warning for format ~!

[Andy Wingo]

Fixed in 90baf8cdfe8ce356ee4720a012e0deb5a2cb5818 by ijp.  Thanks to
all!
-- 
http://wingolog.org/

bug#13544: (web http) fails to parse numeric timezones in Date header

[Andy Wingo]

On Thu 24 Jan 2013 23:13, l...@gnu.org (Ludovic Courtès) writes:

> scheme@(guile-user)> (use-modules(web client)(web uri))
> scheme@(guile-user)> (http-get (string->uri "http://www.sqlite.org/";))
> web/http.scm:768:6: In procedure parse-asctime-date:
> web/http.scm:768:6: Bad Date header: Thu, 24  Jan 2013 21:53:01 +

As you can see here:

  http://pretty-rfc.herokuapp.com/RFC2616#date-time-formats

HTTP doesn't actually support other time zones.  The date header being
reported by sqlite.org is invalid.

Andy
-- 
http://wingolog.org/