l...@gnu.org (Ludovic Courtès) writes:
> Consider this code:
>
> (use-modules (system foreign))
>
> (define %abort
> (dynamic-func "abort" (dynamic-link)))
>
> (let ((ptr (make-pointer 123 %abort)))
> (display "hello\n")
> (gc))
>
> Guile is free to collect ‘ptr’ when ‘gc’ is called since it
Hi,
ro...@web.de writes:
> Hello,
>
> The attached simple test calls free functions with bad smob_tag.
> I see the same stuff with 2.2.0
> There are no errors using the stable 2.0.11 version.
>
> static size_t
> free_box (SCM box_smob)
> {
> if (SCM_TYP16(box_smob) != scm_tc16_box) {
>
Andy Wingo skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Consider this code:
>>
>> (use-modules (system foreign))
>>
>> (define %abort
>> (dynamic-func "abort" (dynamic-link)))
>>
>> (let ((ptr (make-pointer 123 %abort)))
>> (display "hello\n")
>> (gc))
>>
>> Guile is free to colle
On Wed 19 Apr 2017 11:50, l...@gnu.org (Ludovic Courtès) writes:
> I need to chew a bit more on this, but the conclusion is probably that
> my expectations were incorrect, indeed. :-)
OK I close this bug in the meantime then :) Feel free to reopen if
there is a thing to do!
Andy
On Thu 13 Apr 2017 13:25, writes:
> So. (help cons) is no longer working for me with 2.2.
>
> The output of
>
> echo '(help cons)' | strace guile
>
> shows
>
> stat("/usr/local/share/guile/guile-procedures.txt", 0x7ffd5f923330) = -1
> ENOENT (No such file or directory)
> stat("/usr/local/share
On Mon 03 Apr 2017 18:04, John Dulaney writes:
> I am consistently getting the out of memory test to fail on i686 and 64 bit
> Power.
>
> Build logs are as follows:
>
> i686 on Fedora Rawhide (what will be F27):
> https://kojipkgs.fedoraproject.org//work/tasks/4744/18694744/build.log
>
> 64 bit P
On Sat 01 Apr 2017 13:18, Zefram writes:
> The SRFI-19 current-time function can return several flavours of the
> current time:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (current-time time-utc)
> $1 = #
> scheme@(guile-user)> (current-time time-tai)
> $2 = #
> s
On Mon 27 Mar 2017 18:06, Andrew Moss writes:
> I believe I have fixed this bug, but I'm not sure if I put the test
> case in the right place within the file. Please see the attached
> patch.
>
> From e975f8ae8d494985a51faed5b15c5664a557e0e2 Mon Sep 17 00:00:00 2001
> From: Andrew Moss
> Date: M
On Sun 26 Mar 2017 04:09, Zefram writes:
> The ~f format specifier for SRFI-19's date->string is documented as:
>
> #~f seconds and fractional seconds, with locale
> # decimal point, eg. `5.2'
>
> Let's test that example:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> s
thanks
On Fri 24 Mar 2017 17:59, "Stewart, Adam James" writes:
> $ ls -l /usr/lib64/libltdl.so.7*
> lrwxrwxrwx 1 root root 16 Feb 27 11:19 /usr/lib64/libltdl.so.7 ->
> libltdl.so.7.3.0
> -rwxr-xr-x 1 root root 41248 Feb 16 2016 /usr/lib64/libltdl.so.7.3.0
>
> Do you have any suggestions as to how I can
On Sun 26 Mar 2017 04:00, Zefram writes:
> scheme@(guile-user)> (date->string (make-date 55 56 34 12 26 3 2017 0)
> "~f")
> $2 = "56.5e-4"
Thanks for the report. Fixed in the the fix for #26260; added the test
case anyway. Cheers.
Andy
Hi,
On Mon 20 Mar 2017 07:10, Arun Isaac writes:
> In the second line of the argument specification of scheme procedure
> `fold-layout', "handler-pair" is misspelt as "bandler-pair".
Thanks, fixed. Patches welcome in the future too :)
Andy
On Mon 20 Mar 2017 02:39, Matt Wette writes:
> Attached is a patch to apply to guile-2.2.0 to compile on FreeBSD 11.0
> Changes
> 1) updated README to indicate which extra FreeBSD packages need to be
> installed
> 2) minor change to configure.ac (implies autoconf needs to run) to use
> bdw-gc-t
> Thanks, fixed. Patches welcome in the future too :)
Sure, thanks!
On Mon 20 Mar 2017 02:22, Zefram writes:
> As implemented in Guile 2.2.0, the unlisted feature guile-2.2 is also
> recognised by cond-expand.
Added to doc; tx for report.
Andy
On Sun 19 Mar 2017 16:26, Freja Nordsiek writes:
> Small bug I found when using the statprof module when using the
> statprof procedure with a flat display. The summary lines at the end
> are not written to the port provided as an argument and are instead
> written to (current-output-port). A pat
On Sat 18 Mar 2017 23:41, Zefram writes:
> Computing the duration of the period between two UTC times, using
> SRFI-19 mechanisms:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (define t0 (date->time-utc (make-date 0 59 59 23 30 6
> 2012 0)))
> scheme@(guile-user)
On Sat 18 Mar 2017 00:53, Zefram writes:
> The documentation, near the start of the section on SRFI-19, says
>
> !*Caution*: The current code in this module incorrectly extends the
> ! Gregorian calendar leap year rule back prior to the introduction of
> ! those reforms in 1582 (or the approp
On Thu 16 Mar 2017 16:45, Jean Louis writes:
> Hello,
>
> This may help you, it failed on 2.2. Maybe not serious.
>
> Jean
>
> Running peval.test
> Running poe.test
> Running popen.test
> Running ports.test
> warning: call to primitive-fork while multiple threads are running;
> further b
This is an excerpt from the build error for guile, at the step
`make -j12'
--- START --
make all-am
make[3]: Entering directory `/data/gpu/raghav/src/guile-2.0.14/libguile'
CC libguile_2.0_la-alist.lo
CC libguile_2.0_la-arbiters.lo
CC libguile_2.0_la-array
On Fri 17 Mar 2017 14:11, writes:
> Thomas Klausner wrote:
>>
>> SNARF net_db.doc
>> net_db.c:468:***Missing or erroneous `#define FUNC_NAME s_AI_ADDRCONFIG);'
>> net_db.c:488:***Missing or erroneous #undef for AI_ADDRCONFIG);:
>>
>> Compilation continues even though this looks like a
On Wed 15 Mar 2017 14:35, Alejandro Sanchez writes:
> If I define a method named ‘-‘ which only takes in one parameter, the
> expression ‘(- v)’ gets rewritten to ‘(- 0 v)’. Here is a minimal example:
>
> (use-modules (oop goops))
>
> (define-class ()
> (x #:init-valu
On Wed 08 Mar 2017 18:01, Mike Gran writes:
> Hi-
> I created the following file, which I ran under guile-2.0 and master.
> There is no tracing output. What am I misunderstanding?
> (use-modules
> (system vm trace))
>
> (define (write-hi)
> (write "hi"))
>
> (define (outer)
> (write-hi))
>
On Wed 08 Mar 2017 12:07, Alejandro Sanchez writes:
> If I define a ‘zero?’ predicate method for a custom class the primitive
> ‘zero?’ is lost. Here is a simple vector module:
>
> ;;; File vector2.scm
> (define-module (vector2)
> #:use-module (oop goops)
> #:export (
On Tue 07 Mar 2017 16:34, Thomas Danckaert writes:
> It looks like Guile's srfi-37 implementation doesn't process empty
> string arguments correctly. For example, here's a stacktrace I get when
> executing guix system list-generations "":
>
> $ guix system list-generations ""
> Backtrace:
> In i
On Mon 20 Feb 2017 00:02, Sergei Trofimovich writes:
> * doc/ref/api-data.texi: tweak codepoint notation
Applied; thanks!
Andy
On Mon 20 Feb 2017 00:02, Sergei Trofimovich writes:
> * doc/ref/api-procedures.texi: fix typo 'an' -> 'on'
Applied. Thanks :)
Andy
On Sun 19 Feb 2017 23:58, Sergei Trofimovich writes:
> The fix is to ignore -g* flags. They should only affect debugging output.
>
> * libguile/guile-snarf.in: skip -g* arguments to avoid build failure
Applied. Thanks :)
Andy
On Thu 16 Mar 2017 04:11, Matt Wette writes:
> HI saffron,
>
> I have been able to get guile-2.1.8 to build on FreeBSD 11.0.
>
> I had to “pkg install” : pkgconf, gmake, boehm-gc-threaded
>
> Then to work around following config issue, I “pkg install autotools”
> Edit autoconf.ac and find “bdw-gc
On Wed, Apr 19, 2017 at 04:45:14PM +0200, Andy Wingo wrote:
> On Thu 16 Mar 2017 16:45, Jean Louis writes:
>
> > Hello,
> >
> > This may help you, it failed on 2.2. Maybe not serious.
> >
> > Jean
> >
> > Running peval.test
> > Running poe.test
> > Running popen.test
> > Running ports.test
> > wa
Andy Wingo wrote:
>This makes sense to me, FWIW.
Patch attached.
-zefram
>From 444703940983d559935c4dd2a2c89d7888c67119 Mon Sep 17 00:00:00 2001
From: Zefram
Date: Wed, 19 Apr 2017 17:08:30 +0100
Subject: [PATCH] correct note about Gregorian reform in SRFI-19
SRFI-19 specifies proleptic use of
Andy Wingo wrote:
>Makes sense to me. Would you like to submit a patch and test case?
This particular bug has interactions with other bugs that make me
uncomfortable about attempting to fix it right now. The right way to
fix this is especially influenced by the approach taken to bug#22033 and
to
From: Andy Wingo
Subject: Re: bug#26013: (srfi srfi-37) chokes on empty string
parameter
Date: Wed, 19 Apr 2017 17:13:25 +0200
On Tue 07 Mar 2017 16:34, Thomas Danckaert
writes:
It looks like Guile's srfi-37 implementation doesn't process empty
string arguments correctly.
[...]
In srfi/sr
Patch attached.
-zefram
>From 6f9d9b355233b578eb3ce13549c8fdc9d7fb8364 Mon Sep 17 00:00:00 2001
From: Zefram
Date: Wed, 19 Apr 2017 19:02:13 +0100
Subject: [PATCH] signal error of time-difference on differing types
It is an error to apply SRFI-19's time-difference to time structures of
differing
A sequence of two patches is attached. The first fixes the ~2/~4 bug,
signalling an error for any unrepresentable offset.
The second is a bonus patch, which fixes related problems in ~z, the
RFC 822 zone format specifier. Prior to the patch, ~z outputs "Z" for
UT, which would be correct for ISO
Compilation of 2.2.1 fails for me, producing a lot of warnings about
implicit declaration of GC_is_heap_ptr(), and ultimately
CCLD guile
./.libs/libguile-2.2.so: undefined reference to `GC_is_heap_ptr'
collect2: error: ld returned 1 exit status
Makefile:2439: recipe for target 'guile' failed
A patch to fix this is attached. The ISO 8601 date formats were
implemented by using the ~Y formatter for the year portion, but SRFI-19
doesn't require ~Y to follow ISO 8601, so this raises the question of
whether ~Y should. It could be fixed by changing ~Y to conform to
ISO 8601, retaining the e
I wrote:
>I chose the former strategy, partly because the funny non-linear year
>number doesn't seem a useful thing to support in date->string at all,
Sorry, this comment is misplaced. It relates to bug#21903; the choice
about ~Y applies to both of these bugs.
-zefram
A patch to fix this is attached. It applies on top of my patch for
bug#21904. The choice that I described for that bug about whether
to change ~Y or to have a separate ISO 8601 year formatter actually
applies to both bugs, and the comment that I made there about exposing
the non-linear year numbe
40 matches
Mail list logo
