Hi Daniel,
Daniel Hartwig writes:
> * Terminology
>
> The terminology used in latest URI spec. (RFC 3986) is not widely used
> elsewhere. Not by Guile, not by the HTTP spec., or other sources.
> Specifically, it defines these terms:
>
> - URI: scheme rest ... [fragment]
> - Absolute-URI: scheme
On Tue 19 Feb 2013 18:53, Eli Zaretskii writes:
>> + (define (unc-path?)
>> + ;; Universal Naming Convention (UNC) paths start with \\, and
>> + ;; are always absolute.
>> + (string-prefix? "" path))
>
> A UNC file name can also begin with 2 slashes, as in "//foo
On 24 February 2013 18:45, Mark H Weaver wrote:
> Hi Daniel,
>
> Daniel Hartwig writes:
>> * Terminology
>>
>> The terminology used in latest URI spec. (RFC 3986) is not widely used
>> elsewhere. Not by Guile, not by the HTTP spec., or other sources.
>> Specifically, it defines these terms:
>>
>
On Tue 19 Feb 2013 19:00, Eli Zaretskii writes:
>> >* libguile/load.c (scm_init_load_path) [__MINGW32__]: Convert
>> >backslashes to forward slashes in values of GUILE_LOAD_PATH and
>> >GUILE_LOAD_COMPILED_PATH.
>>
>> Is this necessary now that backslash is recognized as a file name
On Wed 28 Nov 2012 16:56, Daniel Hartwig writes:
> A short module, it is not hard to fix, though given all of the above it
> makes sense to simply remove it.
I think removing it is the right thing. Even with your patch it still
won't work because the default "table constructor" is a vector inst
On Fri 27 Jan 2012 09:26, Mark H Weaver writes:
> These are genuine bugs:
>
> language/glil/decompile-assembly.scm:174:21: warning: possibly unbound
> variable `make-glil-local'
> language/glil/decompile-assembly.scm:170:21: warning: possibly unbound
> variable `make-glil-local'
Fixed by remov
> From: Andy Wingo
> Cc: l...@gnu.org, 10474-d...@debbugs.gnu.org
> Date: Sun, 24 Feb 2013 14:25:06 +0100
>
> So with these last commits, hopefully native MinGW builds are supported.
> Would you mind testing again?
Thanks, will do when I have time.
On Sat 28 Jan 2012 11:21, Mark H Weaver writes:
> The R5RS specifies that if 'char-ready?' returns #t, then the next
> 'read-char' operation is guaranteed not to hang. This is not currently
> the case for ports using a multibyte encoding.
>
> 'char-ready?' currently returns #t whenever at least
On Wed 20 Feb 2013 00:38, Jan Schukat writes:
> What happens is, in random.c in random_state_of_last_resort on line 668
> scm_getpid is used to seed the random generator. So either a
> preprocessor switch or a hand constructed scm like in scm_getpid
> (scm_from_ulong(getpid())) should be used the
On Tue 31 Jan 2012 19:47, Mark H Weaver writes:
> Rob Browning writes:
>> Make check fails on the s390x architecture:
> [...]
>> ERROR: incorrect result (7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
>> 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
>> 7 7 7
Hi,
On Mon 30 Jan 2012 04:32, Rob Browning writes:
> Make check fails on the armhf architecture:
>
> /bin/bash: line 5: 31270 Segmentation fault srcdir="." builddir="."
> GUILE_AUTO_COMPILE=0 "../../meta/uninstalled-env" ${dir}$tst
> FAIL: test-with-guile-module
> PASS: test-scm-with-
Daniel Hartwig writes:
> On 24 February 2013 18:45, Mark H Weaver wrote:
>> I would argue that Absolute-URIs are more often appropriate in typical
>> user code. The reason is that outside of URI-handling libraries, most
>> code that deals with URIs simply use them as universal pointers,
>> i.e.
Hi Andy,
Andy Wingo writes:
> On Sat 28 Jan 2012 11:21, Mark H Weaver writes:
>
>> The R5RS specifies that if 'char-ready?' returns #t, then the next
>> 'read-char' operation is guaranteed not to hang. This is not currently
>> the case for ports using a multibyte encoding.
>>
>> 'char-ready?'
Hi :)
On Sun 24 Feb 2013 21:14, Mark H Weaver writes:
> Andy Wingo writes:
>
>> On Sat 28 Jan 2012 11:21, Mark H Weaver writes:
>>
>>> The R5RS specifies that if 'char-ready?' returns #t, then the next
>>> 'read-char' operation is guaranteed not to hang. This is not currently
>>> the case for
Andy Wingo writes:
> On Sun 24 Feb 2013 21:14, Mark H Weaver writes:
>
>> Maybe I'm missing something, but I don't see any semantic problem here,
>> and it seems straightforward to implement. 'char-ready?' should simply
>> read bytes until either a complete character is available, or no more
>>
The current limitation of 10 arguments to foreign functions is proving
to be a problem for some libraries, in particular the Allegro game
library.
Is there a reason why raising this limit to 16 or 20 would be
undesirable? What tradeoffs are involved?
Thanks,
Mark
reopen 13768
thanks
Andy Wingo writes:
> On Wed 20 Feb 2013 00:38, Jan Schukat writes:
>
>> What happens is, in random.c in random_state_of_last_resort on line 668
>> scm_getpid is used to seed the random generator. So either a
>> preprocessor switch or a hand constructed scm like in scm_getpid
On 25 February 2013 08:06, Mark H Weaver wrote:
> Andy Wingo writes:
>
>> On Sun 24 Feb 2013 21:14, Mark H Weaver writes:
>>
>>> Maybe I'm missing something, but I don't see any semantic problem here,
>>> and it seems straightforward to implement. 'char-ready?' should simply
>>> read bytes unti
Hi Hans. Following up on an old bug report:
Hans Aberg wrote:
> bad return from expression `(f-sum -1 2000 -3 400)': expected
> 3971999; got 3972255
> FAIL: test-ffi
This turns out to be due to a bug in LLVM, namely that it improperly
assumes that signed integer arguments w
19 matches
Mail list logo
