I have tried this one on master and it exhibits the results you expect,
not the buggy results. I added the test to the test suite. I don't
plan on devoting resource to fixing this bug in 2.0 though, so I'm
closing it for now. Feel free to reopen if you hvae a patch to fix :)
Andy
On Fri 12 Jul
Hi Christopher,
Thanks for the report. I think no one handled this because the 1.8
series was already not the latest stable release, and given that we're
about to release 2.2 I think it's probably best to close this one. We
welcome new bug reports against the latest 2.0 stable releases, or the
2
Hi Mark,
I know you like mathy things and so this might be a project you would
like. I think the right thing to do here is to redefine fixnum? as
(= x (logand x #x2fff))
on 32-bit targets and 8 more f's for 64-bit targets. Make sure to get
that inline. In that way we'll end up unboxing X
Howdy :)
Three years later, this is now fixed and will be in 2.1.4. I think
we'll cherry-pick it back to 2.0.12 too.
Cheers,
Andy
On Sat 20 Jul 2013 08:57, Göran Weinholt writes:
> Hello schemers,
>
> the fxcopy-bit procedure from (rnrs) is missing some range checks. It
> can return a non-fi
Applied to master, thanks :)
Andy
On Tue 21 Jun 2016 00:33, taylanbayi...@gmail.com (Taylan Ulrich
"Bayırlı/Kammer") writes:
> Pinging this thread with a (very slightly) updated patch. :-)
>
>
> From 7f35d515d711e255bba5a89a013d9d92034edf41 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Taylan=20Ul
Applied, thanks :)
On Tue 21 Jun 2016 00:34, taylanbayi...@gmail.com (Taylan Ulrich
"Bayırlı/Kammer") writes:
> Also pinging this thread with a (very slightly) updated patch. :-)
>
>
> From 17599f6ce7ba0beb100e80455ff99af07333d871 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Taylan=20Ulrich=20Bay=
Andy Wingo skribis:
> On Mon 17 Jun 2013 15:54, ludovic.cour...@inria.fr (Ludovic Courtès) writes:
>
>> When using SA_RESTART, signal handlers are never executed, as in this
>> example (checked on 2.0.9+):
>>
>> (sigaction SIGALRM
>> (lambda (signum)
>> (pk 'sig signum))
>> SA_RESTART)
>>
On Tue 21 Jun 2016 01:36, Linas Vepstas writes:
> On Mon, Jun 20, 2016 at 10:34 AM, Andy Wingo wrote:
>
> On Sat 24 Jan 2015 23:52, Linas Vepstas
> writes:
>
> > I've got a test where hit guile with maybe a dozen threads doing
> > assorted things. Doing this, I then see han
On Tue 21 Jun 2016 09:48, ludovic.cour...@inria.fr (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Mon 17 Jun 2013 15:54, ludovic.cour...@inria.fr (Ludovic Courtès) writes:
>>
>>> When using SA_RESTART, signal handlers are never executed, as in this
>>> example (checked on 2.0.9+):
>>>
>>
Andy Wingo skribis:
> I see this, but I'm not quite sure what's going on. What I do see is
> that par-map of 1+ on a list is horribly slow, both on 2.0 and master.
> Ludovic do you know what's going on here?
As David put it, only one core is being used, which is clearly a bug.
I believe the bu
Ping with CC to Andy. :-)
On Sun 18 Aug 2013 14:14, Göran Weinholt writes:
> Hello schemers,
>
> these identifiers are not exported by the (rnrs) library:
>
> &i/o-decoding
> i/o-decoding-error?
> &i/o-encoding
> i/o-encoding-error-char
> i/o-encoding-error?
> make-i/o-decoding-error
> make-i/o-encoding-erro
Hi!
--disable-posix is intended to be a size reduction thing, not
necessarily a portability hack. Guile should build on MinGW with POSIX
enabled; if it doesn't that's a different bug :) When POSIX support is
enabled we should simply compile out features that aren't detected on
the platform. For
Hi :)
Ignorant question: what is the precision argument good for? FWIW
Guile's inexact reals are all 64-bit doubles.
Just curious :)
Andy
On Tue 20 Aug 2013 14:05, Göran Weinholt writes:
> Hello schemers,
>
> the number->string procedure from (rnrs) should accept the optional
> precision arg
Andy Wingo skribis:
> On Tue 21 Jun 2016 09:48, ludovic.cour...@inria.fr (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> On Mon 17 Jun 2013 15:54, ludovic.cour...@inria.fr (Ludovic Courtès) writes:
>>>
When using SA_RESTART, signal handlers are never executed, as in this
exam
I don't really understand this bug. Ian's investigation isn't right, I
don't think; the "delimited" port stuff from (web response) should make
it correct to call get-bytevector-all on the response port. So I think
there is not a client bug, but there may be a server bug on macOS. Can
you retry o
Hi :)
I dunno how much we should push this "processes are a single port"
abstraction. In many ways for OPEN_BOTH pipes it's easier to deal with
an input and an output port and a PID instead of the pipe abstraction.
WDYT? We could just expose `open-process' from (ice-9 popen) to start
with. It w
Hi Jan,
I believe that Eli Zaretskii builds natively on MinGW. I know we do
cross-build as well. I'm going to archive this bug; please open a new
one if you have a problem with the most recent releases. Thanks!
Andy
On Fri 06 Sep 2013 00:42, "Jan Schukat" writes:
> Hello again,
> I'm trying
Yes!
As Ian notes this needs a test case. Some kind Guixer should fix up
this patch and send to Guile so that it lands before we release 2.0.12,
which should come any day now :-)
Andy
On Sun 06 Oct 2013 21:36, l...@gnu.org (Ludovic Courtès) writes:
> Consider these two modules:
>
> (define-mo
Hi,
On Sun 13 Oct 2013 15:51, l...@gnu.org (Ludovic Courtès) writes:
> $ guile --no-auto-compile -L . -c '(use-modules (system base compile))
> (for-each compile-file (list "one.scm" "two.scm" "three.scm"))'
>
> $ guile --no-auto-compile -L . -c '(use-modules (system base compile))
> (for-each
Hi Frank,
Closing this one due to lack of information. If you find a compile
failure with icc on Guile 2.0.11 or 2.1.3, please open a new report.
Thanks :)
Andy
On Thu 24 Oct 2013 06:20, Ian Price writes:
> "" writes:
>
>> Thanks, Ian.
>>
>> For me compiling guile is just to satisfy a depe
close
thanks
On Sun 20 Oct 2013 13:40, Andreas Metzler writes:
> Hello,
>
> guile-2.0 (2.0.9) does not work on ia64. It builds, but the executable
> segfaults:
>
>
>
> SNARF regex-posix.doc
> GEN guile-procedures.texi
> /bin/bash: line 1: 30416 Broken pipe
Hi,
I don't know what's going on here. It should work! However without any
more info we can't do anything. Please file a new report if you cannot
build Guile 2.0.11 or 2.1.3. Cheers :)
Andy
On Sun 20 Oct 2013 13:40, Andreas Metzler writes:
> Hello,
>
> guile-2.0 (2.0.9) does not work on ia
close
thanks
On Tue 21 Jun 2016 13:24, Andy Wingo writes:
> Hi Frank,
>
> Closing this one due to lack of information. If you find a compile
> failure with icc on Guile 2.0.11 or 2.1.3, please open a new report.
> Thanks :)
>
> Andy
>
> On Thu 24 Oct 2013 06:20, Ian Price writes:
>
>> "" writ
Hi again!
Andy Wingo skribis:
> On Sun 13 Oct 2013 15:51, l...@gnu.org (Ludovic Courtès) writes:
>
>> $ guile --no-auto-compile -L . -c '(use-modules (system base compile))
>> (for-each compile-file (list "one.scm" "two.scm" "three.scm"))'
>>
>> $ guile --no-auto-compile -L . -c '(use-modules (
Hi Jonathan,
Thanks for the report and sorry for never getting back to you. The good
news is that there are new releases of Guile and libgc. The bad news is
that we can't do anything for you on this report, given that there are
new releases and there's not much other info. I know you've probabl
Not really sure what to do here.
Ideally we could just use ~@y in the format messages. However we can't
rely on having a full format loaded up, only simple-format. We could
lazily load the full format when needed, but I don't know if we should
train users that the full `format' is always around.
Hi Zefram,
Thanks for the great report!
I believe this is fixed in v2.1.3. Reproducing the bug is a little
different there but I think I did get it so that Guile should try to
print out the value. I don't know if we would be able to fix this in
2.0 though :/ I am closing because I believe it t
Andy Wingo wrote:
>Thoughts?
How was this managed in Guile 1.8?
It seems that you need the truncated-print mechanism to be always
available internally, but this doesn't require that it be always visible
to the user. You can still require the full libraries to be loaded for
the user to get access
Thoughts, Mark?
On Mon 06 Jan 2014 01:17, Zefram writes:
> Commit 5e7918077a4015768a352ab19e4a8e94531bc8aa says
>
> A note on the rationale for (* 0 +inf.0) being a NaN and not exact 0:
> The R6RS requires that (/ 0 0.0) return a NaN value, and that (/ 0.0)
> return +inf.0. We
No additional info; let's close. Please file a new bug if you have
errors building Guile from git again. Thanks!
Andy
On Wed 15 Jan 2014 19:41, Mark H Weaver writes:
> z_axis writes:
>
>> hi,friends
>> After `git clone git://git.sv.gnu.org/guile.git`, `./autogen` reports:
>> m4: illegal opti
> From: Andy Wingo
> Cc: 14361-d...@debbugs.gnu.org, l...@gnu.org
> Date: Mon, 20 Jun 2016 23:19:24 +0200
>
> Hi Eli :)
>
> Thank you for your ongoing work on MinGW and Guile, it's really
> appreciated. I just wanted to say that explicitly here, even though I'm
> closing this bug, as I underst
On Wed 05 Feb 2014 16:56, Mark H Weaver writes:
> Also: this is on Solaris 10u10. Cole mentioned that on IRC.
On the one hand I don't understand how this can happen. On the other, I
unfortunately don't have faith in the buckets-and-chains weak table
implementation in 2.0; it usually works but
Hi :)
I think we are happy to look at patches to support non-GNU make but
without follow-through from a reporter we aren't going to make efforts
in this direction; too many other things to do :)
If you can track down the issue, please let us know and we'll see what
we can do. Mark, Ludo, feel fr
Hi Kapten!
Looks like a bug in libgc somehow. Did you ever trace this down?
Andy
On Tue 08 Apr 2014 16:45, Kapten Anto writes:
> On my system its quite simple to reproduce, start guile, type ,q
> enter, then start it again and it crashes. In between runs Ive
> verified it does not show up in
Thanks for the report! This is fixed in Guile 2.0.11 and in 2.1.x,
though the full situation is a bit strange.
See: http://thread.gmane.org/gmane.lisp.guile.user/11218/focus=11813
Regards,
Andy
On Sun 27 Apr 2014 03:43, "Diogo F. S. Ramos" writes:
> When using GOOPS, if a class has a second
OK.
On Tue, Jun 21, 2016 at 2:52 AM, Andy Wingo wrote:
> On Tue 21 Jun 2016 01:36, Linas Vepstas writes:
>
> > On Mon, Jun 20, 2016 at 10:34 AM, Andy Wingo wrote:
> >
> > On Sat 24 Jan 2015 23:52, Linas Vepstas
> > writes:
> >
> > > I've got a test where hit guile with maybe a doz
On Thu 16 Oct 2014 02:30, Mark H Weaver writes:
> retitle 17399 Problems building guile-2.0.11 with libunistring 0.9.0
> thanks
>
> Hi Ed,
>
> I finally looked into this test failure that you experienced when
> compiling guile-2.0.11 from source code on Ubuntu 12.04. I see that
> you've since up
Andy Wingo skribis:
> I would like to apply this patch, to master at least. Any objections?
> We need documentation for the new exports, is the only missing thing.
On a quick glance that looks good. My only concern would be
incompatibilities; for instance, the ‘content-location’ can now be an
On Wed 04 Jun 2014 01:11, Mark H Weaver writes:
> Mark H Weaver writes:
>> Sounds good. Specifically, I guess we should deprecate this way of
>> using #:select.
>>
>> If you do this, can you adjust system/repl/coop-server.scm to avoid it?
>> It imports the following private bindings:
>>
>> st
On Mon, Jun 20, 2016 at 10:56 AM, GNU bug Tracking System <
help-debb...@gnu.org> wrote:
> (display "Hòa Phú Phú Tân Hiệp An Tương Bình Hiệp Định Hòa\n" sss)
Yep, it now works for me with guile-2.1.3
--linas
Mark H Weaver wrote:
> I also suspect that (/ 0 ) should be 0,
>although that conflicts with R6RS. We should probably investigate the
>rationale behind R6RS's decision to specify that (/ 0 0.0) returns a NaN
>before changing that, though.
I think R6RS makes sense for (/ 0 0.0). A flonum
Andy Wingo writes:
> Thoughts, Mark?
Sorry for the long delay on this, but briefly, I agree that my rationale
was flawed, and that we should make (* 0 ) == 0 in all cases
in 2.2. I also suspect that (/ 0 ) should be 0,
although that conflicts with R6RS. We should probably investigate the
ration
Hi,
On Tue 13 May 2014 12:47, David Kastrup writes:
> The following code results in an error:
>
> (use-modules (srfi srfi-1))
> (reduce-right + 0 (make-list 1 1))
>
> Backtrace:
> In srfi/srfi-1.scm:
> 379: 19 [recur (1 1 1 1 1 1 1 1 1 ...) (1 1 1 1 1 1 1 1 1 ...)]
> 379: 18 [recur (1 1 1
Hi :)
On Sun 01 Jun 2014 20:40, Mark H Weaver writes:
> Mark Polesky writes:
>> Neither example below should be line-wrapped, but the second one
>> is.
>
> Our pretty printer, inherited from SLIB and originally written by Marc
> Feeley, uses a great many heuristics to make formatting decisions
Andy Wingo skribis:
> On Wed 04 Jun 2014 01:11, Mark H Weaver writes:
>
>> Mark H Weaver writes:
>>> Sounds good. Specifically, I guess we should deprecate this way of
>>> using #:select.
>>>
>>> If you do this, can you adjust system/repl/coop-server.scm to avoid it?
>>> It imports the followi
Hi :)
On Tue 21 Jun 2016 14:01, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Sun 13 Oct 2013 15:51, l...@gnu.org (Ludovic Courtès) writes:
>>> I think the right thing would be to use a separate module hierarchy in
>>> the dynamic extent of ‘compile-file’, somehow, such th
On Tue 21 Jun 2016 14:46, Eli Zaretskii writes:
> I would be happier, though, if the patch for open-process, whose last
> version I submitted here:
>
> https://lists.gnu.org/archive/html/guile-devel/2014-08/msg00015.html
>
> would be admitted to the repository, as it fixes important
> functiona
On Tue 21 Jun 2016 14:38, Zefram writes:
> Andy Wingo wrote:
>>Thoughts?
>
> How was this managed in Guile 1.8?
The printers and the backtrace handling was quite different, but it used
"print states".
> It seems that you need the truncated-print mechanism to be always
> available internally, bu
On Tue 21 Jun 2016 16:52, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Wed 04 Jun 2014 01:11, Mark H Weaver writes:
>>
>>> Mark H Weaver writes:
Sounds good. Specifically, I guess we should deprecate this way of
using #:select.
If you do this, can yo
Andy Wingo skribis:
> On Tue 21 Jun 2016 14:01, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> On Sun 13 Oct 2013 15:51, l...@gnu.org (Ludovic Courtès) writes:
I think the right thing would be to use a separate module hierarchy in
the dynamic extent of ‘compile-
Andy Wingo writes:
> Hi,
>
> On Tue 13 May 2014 12:47, David Kastrup writes:
>
>> The following code results in an error:
>>
>> (use-modules (srfi srfi-1))
>> (reduce-right + 0 (make-list 1 1))
>>
>> Backtrace:
>> In srfi/srfi-1.scm:
>> 379: 19 [recur (1 1 1 1 1 1 1 1 1 ...) (1 1 1 1 1 1 1
On Tue 21 Jun 2016 17:17, l...@gnu.org (Ludovic Courtès) writes:
> Andy Wingo skribis:
>
>> On Tue 21 Jun 2016 14:01, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> Andy Wingo skribis:
>>>
On Sun 13 Oct 2013 15:51, l...@gnu.org (Ludovic Courtès) writes:
>> My "I don't think this is going to
> From: Andy Wingo
> Cc: 14...@debbugs.gnu.org, l...@gnu.org
> Date: Tue, 21 Jun 2016 17:06:05 +0200
>
> Let's give it a go! I understand that you do not want to work with
> gnulib. That's a negative from a Guile POV -- but it's not a
> deal-breaker.
I have nothing against Gnulib, but in this
This is very strange. The build actually managed to run Guile and
compile some stuff then errored. Did you run into this since then?
Were you building with -O0 perhaps?
I see though that there is a macports build of 2.0.11 here:
https://trac.macports.org/browser/trunk/dports/lang/guile/Portfi
Andy Wingo skribis:
> On Tue 21 Jun 2016 16:52, l...@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo skribis:
>>
>>> On Wed 04 Jun 2014 01:11, Mark H Weaver writes:
>>>
Mark H Weaver writes:
> Sounds good. Specifically, I guess we should deprecate this way of
> using #:select.
Fixed in 2.0 and the 2.2 prerelease. Thanks!
Andy
On Sun 14 Sep 2014 23:33, Rob Browning writes:
> [If possible, please preserve the -forwarded address in any replies.]
>
> I suspect this should be fixed, if it hasn't been already.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758971
On Fri 19 Sep 2014 12:28, Andreas Enge writes:
> On Fri, Sep 19, 2014 at 12:16:15PM +0200, Andreas Enge wrote:
>> gcc 4.4.7
>
> It seems to be a problem with the gcc version; with gcc-4.8.3, I get past
> this point. So maybe this bug report can be safely ignored.
I guess given the lack of follow
On Mon 29 Sep 2014 15:24, Daniel Llorens writes:
> The following code:
>
> (define-syntax define-lues
> (syntax-rules ()
> ((_ () exp)
> (call-with-values (lambda () exp) (lambda () 'unspecified)))
> ((_ (var . vars) exp)
> (begin
>(define var (call-with-values (lambda
thanks
On Tue 21 Jun 2016 17:42, Eli Zaretskii writes:
>> From: Andy Wingo
>> Cc: 14...@debbugs.gnu.org, l...@gnu.org
>> Date: Tue, 21 Jun 2016 17:06:05 +0200
>>
>> Let's give it a go! I understand that you do not want to work with
>> gnulib. That's a negative from a Guile POV -- but it's not a
>>
On Thu 02 Oct 2014 14:14, Daniel Llorens writes:
> stable-2.0 with either cut or cute works. The compiler in master works for
> cut but not for cute.
>
> scheme@(guile-user)> (import (srfi srfi-26))
> scheme@(guile-user)> (cute < 1 <> 2)
> While compiling expression:
> ERROR: Wrong number of arg
62 matches
Mail list logo
