On May 2, 2011, at 22:55, Andy Wingo wrote:
> We are brushing the copyright assignment limits here; I'll apply this,
> but if you are interested in sending further patches to Guile, would you
> be OK with assigning copyright to the FSF? Please let me know, and I'll
> send you details in a privat
On Mon 02 May 2011 21:09, Daniel Llorens writes:
> Second try follows. I've noticed the same bug in with-x-to/from-file,
> so I have attempted to fix those too, in the way of
> with-x-to/from-string below.
Looks very nice, thanks!
We are brushing the copyright assignment limits here; I'll apply
On May 2, 2011, at 19:46, Mark H Weaver wrote:
> Daniel Llorens writes:
>> scheme@(guile-user)> (call-with-input-string "hello" (lambda (p) (values 1
>> 2)))
>> $1 = 1
>> $2 = 2
>>
>> but:
>>
>> scheme@(guile-user)> (call-with-input-file "hello" (lambda (p) (values 1 2)))
>> $1 = 1
>
> Indee
Daniel Llorens writes:
> scheme@(guile-user)> (call-with-input-string "hello" (lambda (p) (values 1
> 2)))
> $1 = 1
> $2 = 2
>
> but:
>
> scheme@(guile-user)> (call-with-input-file "hello" (lambda (p) (values 1 2)))
> $1 = 1
Indeed this is suboptimal, and probably a bug.
Thanks for reporting thi
Hello,
I noticed this:
scheme@(guile-user)> (call-with-input-string "hello" (lambda (p) (values 1 2)))
$1 = 1
$2 = 2
but:
scheme@(guile-user)> (call-with-input-file "hello" (lambda (p) (values 1 2)))
$1 = 1
I look up call-with-input-file and I see:
(define (call-with-input-file str proc)
(
