Re: SRFI-105 (curly-infix-expressions) marker #!srfi-105 ... could guile live with that?

2012-09-05 Thread svanleent
David, From a pragmatic side, wouldn't it be better to just have a marker like #!curly-infix. The number 105 doesn't say much when reading the code, which is the whole reason for the existence of curly-infixing. Also, a file extension might change the folding mode. This could by something

Re: SRFI-105 (curly-infix-expressions) marker #!srfi-105 ... could guile live with that?

2012-09-05 Thread David A. Wheeler
svanleent: From a pragmatic side, wouldn't it be better to just have a marker like #!curly-infix. The number 105 doesn't say much when reading the code, which is the whole reason for the existence of curly-infixing. There are advantages either direction. I agree with you on the advantage

things are eq? but not generated at the same time

2012-09-05 Thread Stefan Israelsson Tampe
Hi, I found that this optimization can lead to dangerous bugs. If I put, (define a #(1)) (define b #(1)) , load the file. Then (eq? a b) #t Is this an optimization we need. I can figure out applications where you do not want this behavior e.g. I wan't to make distinct objects and add

Re: things are eq? but not generated at the same time

2012-09-05 Thread Ian Price
Stefan Israelsson Tampe stefan.ita...@gmail.com writes: Is this an optimization we need. I can figure out applications where you do not want this behavior e.g. I wan't to make distinct objects and add metadata by making a vector of it. Now different objects might have the same metadata and

Re: things are eq? but not generated at the same time

2012-09-05 Thread Ian Price
Ian Price ianpric...@googlemail.com writes: anyway. Anyway if vectors are immutable, as I believe they are, it I, of course, meant vector literals, but a quick test shows this is not the case. (define v #(1 2 3)) (pk v) (vector-set! v 0 #f) (pk v) ~ $ guile -s /tmp/test.scm ;;; (#(1 2 3))

Re: things are eq? but not generated at the same time

2012-09-05 Thread Stefan Israelsson Tampe
Yes, I can agree om that. But this should be very stated clearly and perhaps added to a pitfall's section. /Stefan On Wed, Sep 5, 2012 at 9:13 PM, Ian Price ianpric...@googlemail.com wrote: Stefan Israelsson Tampe stefan.ita...@gmail.com writes: Is this an optimization we need. I can

Re: init.scm

2012-09-05 Thread Ludovic Courtès
Hi, Ian Price ianpric...@googlemail.com skribis: Attempting to resolve a guildhall bug with tupi[0], he mentioned init.scm. I was not aware that guile read such a file, and it is not in the manual, but it is in NEWS. So, first off, that situation should change. Agreed. What I would like

Re: things are eq? but not generated at the same time

2012-09-05 Thread Ludovic Courtès
Ian Price ianpric...@googlemail.com skribis: Ian Price ianpric...@googlemail.com writes: anyway. Anyway if vectors are immutable, as I believe they are, it I, of course, meant vector literals, but a quick test shows this is not the case. It could be the case, though. Literal strings are

Re: SRFI-105 (curly-infix-expressions) marker #!srfi-105 ... could guile live with that?

2012-09-05 Thread Ludovic Courtès
Hi David, David A. Wheeler dwhee...@dwheeler.com skribis: Guile support for curly-infix-expressions is very important to me. Yet obviously guile has different semantics for #!, namely, #!...!#. Clearly #!srfi-105 could be handled by a special case, but could people live with that? I even

Re: things are eq? but not generated at the same time

2012-09-05 Thread Ludovic Courtès
Hi, Stefan Israelsson Tampe stefan.ita...@gmail.com skribis: If I put, (define a #(1)) (define b #(1)) , load the file. Then (eq? a b) #t The R5RS reads (info (r5rs) Equivalence predicates): Since it is an error to modify constant objects (those returned by literal