On Sat 09 Mar 2013 02:58, Daniel Hartwig writes:
> -- Scheme Procedure: eval-string string [#:module=#f] [#:file=#f]
> [#:line=#f] [#:column=#f] [#:lang=(current-language)]
> [#:compile?=#f]
>
> we see that there is some potential confusion between the close,
> unescaped (as
On Sat 09 Mar 2013 02:41, Daniel Hartwig writes:
> Interpretting ‘+’ timezone is sensible in a robust implementation,
Yes, I agree, this makes sense.
> though what to do if a numeric timezone is given other than this?
I would continue to raise an error I think. Timezones get complicated,
On Thu 07 Feb 2013 10:12, David Kastrup writes:
> Rationale: GUILE already supports a number of escapes not defined in the
> Scheme standard. Emacs Lisp modes and derivative modes treat opening
> parens in the first column of a file specially, resynchronizing function
> boundaries. The respecti
Hi,
On Fri 01 Mar 2013 17:19, Jan Schukat writes:
> But compiling guile-2.0 on MinGW is a very hairy undertaking. I'm not
> sure how often it is tested by the developers.
Approximately never, unfortunately. However we have been improving it
recently, and cross-compiling from GNU systems to Min
Andy Wingo writes:
> On Thu 07 Feb 2013 10:12, David Kastrup writes:
>
>> Rationale: GUILE already supports a number of escapes not defined in the
>> Scheme standard. Emacs Lisp modes and derivative modes treat opening
>> parens in the first column of a file specially, resynchronizing function
On Sat 09 Mar 2013 02:27, Daniel Hartwig writes:
> It is anyway clear that ‘response-body-port’ is missing the case where
> a content-length header is not present and the body is terminated by
> the server closing the port. Some additional care needs to be taken,
> e.g. ‘#:keep-alive?’ is incomp
On Sat 02 Mar 2013 19:13, Andy Wingo writes:
> Picking up an old thread. What do people think about the attached
> patch? It preserves arity checking for case-lambdas defined in the same
> compilation unit. Case-lambdas are converted to nullary procedures in
> the last minute, before compiling
On Sat 02 Mar 2013 22:41, l...@gnu.org (Ludovic Courtès) writes:
> Looks good. My main grief would be that it makes guile.m4 depend on
> pkg.m4, which we don’t distribute ourselves. And so this may cause
> “PKG_PROG_PKG_CONFIG: command not found” bug reports.
We can just tell people to cat pkg.
Hi,
On Sun 03 Mar 2013 08:01, Thien-Thi Nguyen writes:
> () Andy Wingo
> () Sat, 02 Mar 2013 19:42:19 +0100
>
>I pushed it to a branch a year ago but it never got review. Here's
>the patch, rebased and attached. I'll commit it soon if there are no
>objections.
>
> Not an objection
Hi,
Thanks for the report.
On Fri 08 Mar 2013 09:14, wang writes:
> When compile guile 2.0.7, I got such error:
> make[3]: Entering directory `/home/wangwangwar/desktop/guile-2.0.7/libguile'
> CC libguile_2.0_la-fports.lo
>
> fports.c: In function 'fport_input_waiting':
> fports.c:613:1
On Sat 09 Mar 2013 01:52, Daniel Hartwig writes:
>> Mind the 'REFFIXME'.
>
> Is that the issue you are reporting?
>
> Marks such as this (e.g. ‘FIXME’, ‘TODO’) appear in many places as a
> reminder to fix or work on something in the future. I suppose in this
> case it is to cross-reference with
Yeah. That’s cool. I am a newbie to Scheme. Guile is great. Good job every
one ! Happy hacking.
On Mar 9, 2013 7:24 PM, "Andy Wingo" wrote:
> On Sat 09 Mar 2013 01:52, Daniel Hartwig writes:
>
> >> Mind the 'REFFIXME'.
> >
> > Is that the issue you are reporting?
> >
> > Marks such as this (e.g.
Sorry for the long time waiting. As I said, I had to get some real work
done.
Just tried it again on windows/mingw with the newer tarball:
http://hydra.nixos.org/build/4290536/download/3/guile-2.0.7.157-929d1.tar.gz
This one to be exact. On windows7 with mingw this is the result:
checking fo
On 03/09/2013 10:32 AM, Andy Wingo wrote:
Hi,
On Fri 01 Mar 2013 17:19, Jan Schukat writes:
But compiling guile-2.0 on MinGW is a very hairy undertaking. I'm not
sure how often it is tested by the developers.
Approximately never, unfortunately. However we have been improving it
recently, an
Daniel Hartwig:
> Indeed. There is a distinction between the end-of-file _object_
> (Scheme) and end-of-transmission _character_ (ASCII ^D). The two are
> not equivalent, ...
Sure.
> and when read-char and peek-char return the former
> value it is only to signal a _current_ lack of characters a
On Sat, Mar 09 2013, Andy Wingo wrote:
> On Sat 09 Mar 2013 02:27, Daniel Hartwig writes:
>
>> It is anyway clear that ‘response-body-port’ is missing the case where
>> a content-length header is not present and the body is terminated by
>> the server closing the port. Some additional care needs
On Sat 09 Mar 2013 14:44, Jan Schukat writes:
> Just tried it again on windows/mingw with the newer tarball:
>
> http://hydra.nixos.org/build/4290536/download/3/guile-2.0.7.157-929d1.tar.gz
FWIW it seems hydra is totally down right now; of course that would
happen as soon as ludo goes on holiday
On 9 March 2013 16:21, Andy Wingo wrote:
> On Sat 09 Mar 2013 02:41, Daniel Hartwig writes:
>
>> Interpretting ‘+’ timezone is sensible in a robust implementation,
>
> Yes, I agree, this makes sense.
>
>> though what to do if a numeric timezone is given other than this?
>
> I would continue t
Oh, a present :)
On 10.03.2013, at 00:06, Andy Wingo wrote:
> On Sat 09 Mar 2013 14:44, Jan Schukat writes:
>
>> Just tried it again on windows/mingw with the newer tarball:
>>
>> http://hydra.nixos.org/build/4290536/download/3/guile-2.0.7.157-929d1.tar.gz
>
> FWIW it seems hydra is totally
On 10 March 2013 06:59, Jason Earl wrote:
> On Sat, Mar 09 2013, Andy Wingo wrote:
>
>> On Sat 09 Mar 2013 02:27, Daniel Hartwig writes:
>>
>>> It is anyway clear that ‘response-body-port’ is missing the case where
>>> a content-length header is not present and the body is terminated by
>>> the s
On 9 March 2013 16:25, Andy Wingo wrote:
> Should we remove the brackets entirely? i.e
I would not. The brackets are fairly standard for optional arguments.
On 10 March 2013 01:11, David A. Wheeler wrote:
> Daniel Hartwig:
>> and when read-char and peek-char return the former
>> value it is only to signal a _current_ lack of characters and should
>> not be considered part of the character stream read from the port.
>
> If I understand you correctly, t
Ok, tried the windows builds again.
The struct timespec is still an issue in a mingw build on windows, but I know
how to handle it.
On 10.03.2013, at 00:06, Andy Wingo wrote:
> On Sat 09 Mar 2013 14:44, Jan Schukat writes:
>
>> Just tried it again on windows/mingw with the newer tarball:
>>
23 matches
Mail list logo
