Re: [PATCH] add SRFI: srfi-121; generators

Hi Arthur, "Arthur A. Gleckler" writes: > It's not a bad idea for the sample implementation to be as clear as > possible at the expense of performance. I agree that it's desirable for one of the sample implementations to be as simple and clear as possible, for the purpose of clarifying the speci

Re: [PATCH] add SRFI: srfi-121; generators

Hi John, John Cowan writes: > Mark: I'm interested to know if you have a sketch of ideas for a more > efficient implementation of SRFI 121/158. You say it requires specific > knowledge of Guile internals, but are you willing to sketch how you might > do it? Thanks. Here are a few suggestions

Re: [PATCH] add SRFI: srfi-121; generators

Hi John, John Cowan wrote: > Mark Weaver wrote in July 2019: > >> Also, the provided implementations of 'generator-find', 'generator-any' >> and 'generator-every' are incorrect: > > > I appreciate your finding these bugs. I wish, however, that you had also > sent them to . Sorry about that.

Re: guile 3 update, halloween edition

>> For the record, the bijection between R6RS conditions and Guile's throw >> arguments was my work, not Julian's. > > An honest mistake on my part. My sincere apologies! Thank you, Andy, I appreciate this. Thanks also for asking for input on the mailing list. I'm heavily overloaded at the mome

Re: guile 3 update, halloween edition

Mark H Weaver writes: > Andy Wingo writes: > >> [...] There will be bijections >> between a Guile's "throw" arguments and structured exceptions, mostly >> inspired with what Julian did in the R6RS layer already. > > For the record, the biject

Re: guile 3 update, halloween edition

Andy Wingo writes: > So, now the pending task is to somehow get a condition/exception > hierarchy into Guile core. I will try to mostly push things off to side > modules but it won't always be possible. There will be bijections > between a Guile's "throw" arguments and structured exceptions, mo

Re: Contributions to “Guile Studio”

Hi Ricardo, Ricardo Wurmus writes: > some months ago I thought it would be neat if we had a simpler > environment for newcomers to play with Guile than to ask them to first > learn how to use Emacs. > > This is what made me play around with Emacs to build something called > “Guile Studio”. It a

Re: conflicts in the gnu project now affect guile

Taylan Kammer writes: > Really, I cannot stress it enough how refreshing it is to see the levels > of rationality and kindness in the discussions here, when compared to > most other places on the Internet. I tend to agree that this is generally a very friendly community. Obviously this thread has

Re: conflicts in the gnu project now affect guile

Eli Zaretskii wrote: >> From: Christopher Lemmer Webber >> Date: Wed, 16 Oct 2019 11:33:11 -0400 >> Cc: Andy Wingo >> >> I'm extremely saddened to see RMS pull this move. It seriously >> undermines faith for maintainers of GNU projects that ther is any >> semblance of fair governance, and that

Re: conflicts in the gnu project now affect guile

[resending with fixed headers, for proper threading] Hi Christopher, Christopher Lemmer Webber wrote: > I think *RMS's* action of unilaterally re-appointing Mark without > notifying or asking the other maintainers Did you not see my recent correction about this? I CC'd you, but maybe something

Re: conflicts in the gnu project now affect guile

Hi Christopher, Christopher Lemmer Webber wrote: > I think *RMS's* action of unilaterally re-appointing Mark without > notifying or asking the other maintainers Did you not see my recent correction about this? I CC'd you, but maybe something went wrong. Please see: https://lists.gnu.org/arc

Re: conflicts in the gnu project now affect guile

Hi Jan, Jan Nieuwenhuizen writes: > Mark H Weaver writes: > >> Andy Wingo writes: >>> Before the RMS/GNU/FSF conversation started, Mark Weaver left Guile, for >>> essentially unrelated reasons. He threatened to leave because he wished >>> to be consulte

Re: conflicts in the gnu project now affect guile

Hello all, I just realized that I made a mistake, and my mistake has caused people to strongly condemn RMS for something that he did not actually do. RMS has not yet appointed me as a co-maintainer. To my knowledge, the only thing he has done so far is to *ask* me if I wanted to be appointed co-

Re: conflicts in the gnu project now affect guile

Hi Andy, Andy Wingo writes: > Before the RMS/GNU/FSF conversation started, Mark Weaver left Guile, for > essentially unrelated reasons. He threatened to leave because he wished > to be consulted before I landed mixed definitions and expressions and > shipped them in the 2.9.4 release; The funny

Stepping back up as a co-maintainer

Hello all, In light of recent events, I've decided to step back up as a co-maintainer of GNU Guile. Thanks, Mark

Re: GNU Guile 2.9.4 Released [beta]

Hi Thomas, Thomas Morley writes: > Am Mo., 26. Aug. 2019 um 19:10 Uhr schrieb : >> >> Perhaps you have to add /usr/local/lib to /etc/ld.so.conf (or some >> file below /etc/ld.so.conf.d) and run ldconfig. >> >> HTH >> -- tomás > > Hi tomás, > > thanks for your hints. > I've got it work by running

Re: Support Websocket status code

Hi, Nala Ginrut writes: > Hi folks! > The current response builder will reject status code less than 600: > ---code- > ((not (and (non-negative-integer? code) (< code 600))) > (bad-response "Bad code: ~a" code)) > ---

Re: Now crashing [was Re: guile-2.9.2 and threading

Hi Linas, Linas Vepstas writes: > However -- if one does call `scm_error` fairly rapidly, from multiple > threads, one will eventually hit a race condition and get a crash. If you could produce a small, self-contained example demonstrating this, it would enable us to investigate further.

Re: Should an enclosing let keep the compiler from handling define-module?

Hi Rob, Rob Browning writes: > This doesn't work with 2.2.4: > > (eval-when (expand load eval) > (let ((ignored #t)) > (define-module (bar) > #:use-module (has-foo)) > (format #t "foo: ~s\n" (foo > > producing: > > ERROR: In procedure %resolve-variable: > Unboun

Re: Should letrec via syntax work within eval-when (expand load eval)?

Hi Rob, Rob Browning writes: > Rob Browning writes: > >> I narrowed down an issue I'd hit to this: >> >> ;; somefile.scm >> (define-syntax foo >> (syntax-rules () >> ((_ any ...) (letrec ((x y) (y 'foo)) x >> >> (eval-when (expand load eval) (foo 1)) > > Wait, maybe that's j

Re: Now crashing [was Re: guile-2.9.2 and threading

Hi Linas, > Investigating the crash with good-old printf's in libguile/vm.c produces > a vast ocean of prints ... that should have not been printed, and/or should > have been actual errors, but somehow were not handled by scm_error. > Using today's git pull of master, here's the diff containing a

Re: [PATCH] add SRFI: srfi-121; generators

Hi again, I wrote earlier: > With this in mind, if SRFI-121 is to be added to Guile, it should be a > high performance implementation. The implementation that you provided, > which I guess is primarily taken from the sample implementation, is far > too inefficient, at least on Guile. I should em

Re: [PATCH] add SRFI: srfi-121; generators

Hi Amar, > SRFI-121 Generators. > > All tests(49/49) are passing in my testing. I am not sure if the tests > file is put in the correct place. > > From 0352f9be13aba1e8acc9a8f700f3673334d48d28 Mon Sep 17 00:00:00 2001 > From: Amar Singh > Date: Mon, 1 Jul 2019 05:14:53 +0530 > Subject: [PATCH] ad

Re: C calling Scheme and garbage collection

Hi Isaac, Isaac Jurado writes: > I'm playing with event loop libraries implemented in C (libev, > libevent, etc... in my case libsystemd), but configuring them from > Guile. > > The qsort example in the documentation [1] seems safe because the > qsort C function directly calls back, so the callb

Re: Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?)

Hi Ludovic, Ludovic Courtès writes: > Mark H Weaver skribis: > >> I've finished my updates to the NEWS file in preparation for the 2.2.5 >> release. Feel free to reorganize, edit, or expand on the NEWS entries >> as you think best. I believe that all of the r

Re: Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?)

Hi Ludovic, I've finished my updates to the NEWS file in preparation for the 2.2.5 release. Feel free to reorganize, edit, or expand on the NEWS entries as you think best. I believe that all of the relevant changes are listed, anyway. Note that GUILE-VERSION still needs to be updated. See belo

Re: [PATCH] Fix texinfo->html for @i, @math, @tie and @dots

Christopher Baines writes: > I spotted the following warnings when converting some texinfo to HTML > (for Guix package descriptions). > > ;;; WARNING (Don't know how to convert *braces* to HTML) > ;;; WARNING (Don't know how to convert dots to HTML) > ;;; WARNING (Don't know how to convert i to H

Likely bug in scm_port_poll

Hi Andy, If you'd be willing to take a quick look at this, I'd be grateful. Probably a bug, but I feel uneasy that I might be overlooking something. scm_port_poll contains the following code: if (scm_i_string_contains_char (events, 'r')) c_events |= POLLIN; if (scm_i_string_contains_char

Re: Feedback for #21076

Hi Isaac, Isaac Jurado writes: > Thanks! There's no rush. But I wanted to merge it before 2.2.5 I'm sorry, but it's unlikely to be included in 2.2.5, which will be released very soon. I won't have time to investigate the issues around your proposed patch before then. Mark

Re: Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?)

Hi Ludovic, Ludovic Courtès writes: > Mark H Weaver skribis: > >> Ludovic Courtès writes: >>> What would you think of releasing ‘stable-2.2’ as 2.2.5? >> >> I think it's a fine idea. > > Awesome. We’ll have to update NEWS; I can give it a go,

Re: Feedback for #21076

Hi Isaac, Isaac Jurado writes: > Apologies in advance if this is unorthodox. I just wanted to ping the > list because I sent a patch proposal to fix #21076. Since it's almost > 4 years old and I'm not sure if the bug tracking system notifies > properly. > > https://bugs.gnu.org/21076 I did al

Distributed verification of release tarballs using Guix? (was Re: Releasing 2.2.5?)

Hi Ludovic, Ludovic Courtès writes: > What would you think of releasing ‘stable-2.2’ as 2.2.5? I think it's a fine idea. > It’s great if you can do it, Mark, but otherwise I can do it. Regrettably, Guile 2.2 has become too heavy to build on the only machine in my possession that I have any tru

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Hi Arne, Arne Babenhauserheide writes: > I don’t understand the implications of this, but I realized that I would > love to have info about the sizes of different datastructures in Guile. Sure. > I recently started measuring how much memory is required for a record > compared to a list, so I c

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Ludovic Courtès writes: > Though an immediate, like a fixnum or an iflo, is still something > different from a tagged heap object like a pair, right? I should clarify that in this new approach, a pair is *not* a tagged heap object. Tagged heap objects are those which have a tag in their first wo

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Hi Ludovic, Ludovic Courtès writes: > Though an immediate, like a fixnum or an iflo, is still something > different from a tagged heap object like a pair, right? So I would > expect SCM_THOB_P to be a different test, not a drop-in replacement for > SCM_NIMP, is that correct? That's right. It's

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

I should mention that I'm very open to suggestions Andy might have about any of this. The new approach I'm currently working on with tagged pair pointers requires changes to both the VM and the compiler, and I'm not confident that I've made the best choices there. I've made some preliminary choic

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Hi Ludovic, Ludovic Courtès writes: > As Dave Thompson wrote on IRC yesterday, this can make a significant > difference for applications such as graphics and game engines. Yes, it's especially important to be able to avoid heap allocation in games, where GC pauses can be painful. However, any a

Re: GNU Guile 2.9.2 Released [beta]

Hi Andy, I finally got a chance to look closely at your recent work on Guile 3, and I just wanted to say that the code looks great, a pleasure to read and hack on. Thanks again for your sustained injection of awesomeness into Guile and our community. I probably don't say that enough. Mark

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Mark H Weaver writes: > Here's the format of fixrats on 64-bit systems: > > Srrx0111 > |\/\___/\__/ > | | |

Re: guile-2.9.2 and threading

Mark H Weaver writes: >> Two are stuck here: >> >> #0 __lll_lock_wait () at >> ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 >> #1 0x7f343ca69bb5 in __GI___pthread_mutex_lock ( >> mutex=mutex@entry=0x7f343d4f0f40 ) >>

Re: guile-2.9.2 and threading

Hi Linas, Linas Vepstas writes: > I'm trying to understand how scm_jit_enter_mcode leads to > scm_timed_lock_mutex ... This simply means that 'lock-mutex' was called from Scheme, and specifically from Scheme code that has been compiled to machine code by our JIT compiler. > I want to know who

Re: Immediate doubles (up to 2^256) and rationals coming to Guile 3

Earlier I wrote: > There's also a nice way to extract the denominator from a fixrat: mask > out the sign bit, shift right 5 bits, and interpret it as an IEEE > double. The denominator will be the integer part of the resulting > value, with the numerator in the fraction bits. Simply cast this dou

Immediate doubles (up to 2^256) and rationals coming to Guile 3

I've found a way to efficiently support both immediate IEEE binary-64 doubles up to ~1.158e77 (with larger ones transparently allocated on the heap), and also immediate exact rationals with up to 54 binary digits (~16 decimal digits), without restricting the 64-bit pointer space at all, and without

Re: [PATCH] Add current-suspendable-io-status parameter

Hi Nala, Nala Ginrut writes: > On Thu, May 16, 2019 at 8:59 AM Mark H Weaver wrote: > >> What about when we write something more structured, such as writing a >> large S-expression using 'write', or serializing XML from SXML. In >> those cases, it's eve

Re: Bringing back gc-live-object-stats

Amirouche Boubekki writes: > I am stuck with a memory leak. I think gc-live-object-stats [0] would help. > > [0] > https://www.gnu.org/software/guile/manual/html_node/Garbage-Collection-Functions.html#index-gc_002dlive_002dobject_002dstats > > Can some explain to me how to bring it back? I don'

Re: [PATCH] Add current-suspendable-io-status parameter

Hi Nala, Nala Ginrut writes: > I think your approach works for the cases which use put-bytevector* directly. > Are you assuming the server-core only handles suspendable-port with > put-bytevector in http-read or http-write? > If so, then your approach is not enough. If you're not using 'put-byt

Re: [PATCH] Add current-suspendable-io-status parameter

Hi Nala, Nala Ginrut writes: > On Tue, May 14, 2019 at 7:01 AM Mark H Weaver wrote: >> I guess what you want is the ability to see incremental reports on the >> progress of your large I/O operations. Is that right? If we are going >> to add an API for this, it need

Re: Failed to configure Guile due to dirty iConvert

Hi Jeffrey, Jeffrey Walton writes: > I'm attempting to test GnuTLS using Asan. All dependent libraries need > to be built with Asan, too. That caught Guile in the net. > > Guile 2.2.4 is failing to configure due to resource leaks in the M4 > macro for iconv. See below. Fixed in commit 65d98d8fd2

Re: [PATCH] Add current-suspendable-io-status parameter

Hello again, Previously I wrote: > I also have doubts about the utility of the information provided. > 'start' seems completely irrelevant, since it merely indicates the > position within the read/write buffer. It's easier to make a case that > 'count' might be relevant, but it's not a reliable i

Re: [PATCH] Add current-suspendable-io-status parameter

Hi Nala, Nala Ginrut writes: > Here's a patch to add current-suspendable-io-status: > Its result is a pair: (finished-bytes . rest-bytes) > > This is useful for designing a proper scheduler algorithm for > suspendable I/O operations. > For example, the server-core based on delimited-continuation

Re: Startup locale and environ_locale_charset

Hi Mike, Mike Gran writes: > Starting in the 2.2.x series, the Guile executable calls > setlocale(LC_ALL,"") on startup except when the GUILE_INSTALL_LOCALE > environment variable is set to '0'. > > This leads to a call to scm_shell that converts command line arguments > to Guile strings using t

Re: Unexpectedly low read/write performance of open-pipe

pendable I/O support for custom binary ports, and in particular for these OPEN_BOTH pipe ports. Note that I've not yet done much testing of these patches, besides running the Guile test suite. Mark >From 14dec723707ee766642397962fa93124d9c86811 Mon Sep 17 00:00:00 2001 From: Ma

Re: Undefined Behavior sanitizer findings

Hi Jeffrey, Jeffrey Walton writes: > Guile 2.2.4 built with -fsanitize=undefined on Fedora 29, x86_64. > 'make check' is producing UBsan findings. > > UBsan operates on real data. All of the findings are valid. > > Search for 'runtime error' in the log. Thanks very much for this, and sorry for

Re: Unexpectedly low read/write performance of open-pipe

ector-some', although I haven't yet given them much testing. Mark >From 271cbbc3acc40926c8311e8dcca757285a53f00d Mon Sep 17 00:00:00 2001 From: Mark H Weaver Date: Sun, 14 Apr 2019 17:43:30 -0400 Subject: [PATCH] DRAFT: Add a suspendable implementation of 'get-bytevector-some'. --- module/ice-9/s

Re: [PATCH] Fix gc.test "after-gc-hook gets called" failures

Hi Andrea, Andrea Azzarone writes: > "after-gc-hook gets called" test randomly fails as reported > downstream, for example: > - https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31776 > - https://bugs.launchpad.net/ubuntu/+source/guile-2.2/+bug/1823459 > > I'm attaching a patch that seems to fix the

Re: Unexpectedly low read/write performance of open-pipe

Hi again, Earlier, I wrote: > I'm not sure off-hand what would be required to re-implement custom > ports in suspendable Scheme code. I finally dug into this code, and was delighted to find that Andy Wingo has already laid the groundwork to avoid going through C code in our custom port handlers,

Re: Unexpectedly low read/write performance of open-pipe

Chris Vine writes: > On Tue, 09 Apr 2019 04:35:38 -0400 > Mark H Weaver wrote: >> >> I think it's probably fine for 2.2, although a more careful check should >> be made for differences in behavior between the old and new >> implementations, and tests should be

Re: Unexpectedly low read/write performance of open-pipe

Hi Chris, Chris Vine writes: > On Tue, 09 Apr 2019 04:35:38 -0400 > Mark H Weaver wrote: >> >> I think it's probably fine for 2.2, although a more careful check should >> be made for differences in behavior between the old and new >> implementations, and

Re: Unexpectedly low read/write performance of open-pipe

Hi Rob, Rob Browning writes: > Mark H Weaver writes: > >> See below for a draft reimplementation of the OPEN_BOTH mode of >> open-pipe* based on R6RS custom binary input/output. On my machine it >> increases the speed of your test by a factor of ~1k. > > Hah,

Re: Unexpectedly low read/write performance of open-pipe

. See below for a draft reimplementation of the OPEN_BOTH mode of open-pipe* based on R6RS custom binary input/output. On my machine it increases the speed of your test by a factor of ~1k. Let me know how it works for you. Regards, Mark >From 4612e23994a012ef97e345a927fe9d0f232e78

Re: make-c-struct and pointer->string

Hi David, David Pirotte writes: >> 'make-c-struct' copies the C pointers from those foreign pointer objects, >> but not >> not keep a reference to the objects themselves. > > To me, this sounds very counter intuitive, actually, it sounds like a bug, > make-c-struct should be holding a referenc

Re: make-c-struct and pointer->string

Hi David, David Pirotte writes: >> 'make-c-struct' copies the C pointers from those foreign pointer objects, >> but not >> not keep a reference to the objects themselves. > > To me, this sounds very counter intuitive, actually, it sounds like a bug, > make-c-struct should be holding a referenc

Re: make-c-struct and pointer->string

Hi David, David Pirotte writes: > Hello, > > guile 2.2.4.1-cdb19 > > ,use (system foreign) > > ;; this fails > > scheme@(guile-user)> (make-c-struct (list '* '*) (list (string->pointer > "hello ") (string->pointer "there!"))) > $16 = # > scheme@(guile-user)> (parse-c-struct $16 (list '* '

Re: [PATCH] Support ~N in SRFI-19 string->date

Hi Daniel, Daniel Llorens writes: > The previous patch had a broken test. New attempt, tested on stable-2.2. The revised tests are still broken. > diff --git a/test-suite/tests/srfi-19.test b/test-suite/tests/srfi-19.test > index 4d79f1043..256ff74a0 100644 > --- a/test-suite/tests/srfi-19.test

Re: [PATCH] Support ~N in SRFI-19 string->date

Hi Daniel, Daniel Llorens writes: > The previous patch had a broken test. New attempt, tested on stable-2.2. Looks good to me. Please push! Thanks, Mark > From 53ebca4c8c439148dcdf9990714aaea2a1bc6305 Mon Sep 17 00:00:00 2001 > From: Daniel Llorens > Date: Mon, 10 Dec 2018 11:57

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > Am Mi., 21. Nov. 2018 um 04:38 Uhr schrieb Mark H Weaver : > > I'm not aware of any language in the R[567]RS that makes it clear > whether '...' should be recognized as an ellipsis if it is bound to a > variable. The

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > Am Mi., 21. Nov. 2018 um 04:38 Uhr schrieb Mark H Weaver : > > > Ellipsis identifiers are a bit more tricky, because unlike other > > bindings, the user-visible ellipsis identifiers are not actually > > substituted.

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > > Let's run the following example: > > > > (eval-when (expand) > > (define-syntax bar > > (syntax-rules () > > ((_ stx) > >(syntax-case stx () > > ((_ a (... ...)) > > #'#t) > > ((_ a b c) > >

Re: Compiling guile-2.2.4 for mingw

Mike Gran writes: > On Tue, Nov 20, 2018 at 06:16:32PM +0100, Christoph Buck wrote: >> Is there currently no way to get guile running under mingw-64bit? My plan >> was to integrate guile in a project of mine which currently only builds >> under 64bit. > > Well anything is possible, of course. Her

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > Am Fr., 16. Nov. 2018 um 01:01 Uhr schrieb Mark H Weaver : > > With this in mind, let's examine your example above more closely. The > ellipsis binding for 'e' is only in the transformer environment when the > 'sy

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > > Let's assume we are writing a macro that reimplements syntax (or some > > variation thereof) and which has to check whether identifiers are > > ellipses. For example, the following could be given: > > > > (with-ellipsis e > > (my-syntax a e) >

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > > So what we actually need is a procedure of > > two arguments: `(ellipsis? e ctx)' returns `#t' if the identifier `e' > > is the current ellipsis in the lexical environment of the identifier > > `ctx'. > > Hmm. I don't actually see a need for the

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > Am Mi., 14. Nov. 2018 um 20:11 Uhr schrieb Mark H Weaver : > > > The `ellipsis?' procedure in psyntax.ss does exactly this, but it > > isn't available to user code. Re-implementing it is not possible > > without a

Re: Feature request: Expose `ellipsis?' from psyntax.ss

Hi Marc, Marc Nieper-Wißkirchen writes: > Guile includes a mechanism to specify a custom ellipsis for > `syntax-case' macros. For macro writers it would be nice if there were > a way to check whether a given identifier is the current (custom) > ellipsis. > > The `ellipsis?' procedure in psyntax.

Re: Proposal for a new (ice-9 history)

Hi Mikael, Mikael Djurfeldt writes: > On Tue, Oct 30, 2018 at 1:26 AM Mark H Weaver wrote: > > Mikael Djurfeldt writes: > > > The interface of (value-history) would instead have a lazy-binder > > which provides a syntax transformer for every $... actua

Re: Officially require GNU Make to build Guile? (was Re: Bootstrap optimization)

Hi Mikael, Mikael Djurfeldt writes: > But, as you concluded, Guile currently uses GNU Make specific > functionality. $(filter-out ...) in bootstrap/Makefile.am is such a > case and also the vpath and %-thingies in am/bootstrap.am. I guess you're right. > Probably, you should start out by makin

Re: Proposal for a new (ice-9 history)

Mikael Djurfeldt writes: > The interface of (value-history) would instead have a lazy-binder > which provides a syntax transformer for every $... actually being > used. The $... identifier would expand into a list-ref into the value > history. A few more suggestions: If I write (define (foo x)

Re: Proposal for a new (ice-9 history)

Hi Mikael, Mikael Djurfeldt writes: > I'd like to rewrite (ice-9 history) to conform to the full GDB value > history syntax. This is because I find that I miss being able to refer > to "the last value" etc. Yes, I've also missed this! > Currently we have: > > $ the N:th value from the start >

Officially require GNU Make to build Guile? (was Re: Bootstrap optimization)

Hi Mikael, Mikael Djurfeldt writes: > OK, here's a new patch. OK to apply it? > > This actually also fixes the existing problem of all bootstrap objects > being rebuilt of eval.scm is touched. Very nice! I didn't know about this feature in GNU Make. > The patch is verified to give a faster bu

Re: Bootstrap optimization

Hi Mikael, Mikael Djurfeldt writes: > I find that the attached patch saves a few minutes for parallel builds > on a four core machine. What it does is to build both eval.go and > psyntax.pp.go serially before the rest is built in parallel (when make > is given -j). > > Here's an attempt at expla

Re: Add dependency on texinfo in README

Mikael Djurfeldt writes: > Does this make sense (see attached patch)? > > Forgetting to install the texinfo packages has bitten myself several times. Sure, looks good to me. Thanks! Mark > From 732fe1af508aeb65588981839dfc01172ec79f0e Mon Sep 17 00:00:00 2001 > From: Mikael Djurfeld

Re: [PATCH] Let (format) used in exceptions be overriden

Hi Daniel, daniel.llor...@bluewin.ch writes: > From: Daniel Llorens > > * module/ice-9/boot-9.scm (exception-format): new variable. Globally > replace uses of (format) by (exception-format). What's the rationale for this proposed change? All but one of the occurrences of 'format' that you re

Re: Incorrect documentation for system, system*, and/or waitpid?

Hi Chris, Chris Marusich writes: > Mark H Weaver writes: > >> [...] I wonder if it would be enough to simply change "process status >> code" to "integer status value" [...]. > > I agree. I've attached a new patch that makes the change. It also

Re: Incorrect documentation for system, system*, and/or waitpid?

Hi Chris, Chris Marusich writes: > Mark H Weaver writes: > >>> scheme@(guile-user)> (status:exit-val $1) >>> $5 = 0 >>> scheme@(guile-user)> (status:exit-val $3) >>> $6 = 0 >> >> Right, these procedures are meant

Re: Incorrect documentation for system, system*, and/or waitpid?

Hi Chris, Chris Marusich writes: > I was reading about the "system" and "system*" procedures in the Guile > manual, and it seems like the actual behavior of Guile seems to > contradict what the manual says. I'm using Guile version 2.2.4. > > The Guile manual says that these procedures return th

Re: tree-il begin deprecated?

Hi Matt, Matt Wette writes: > I noticed that from 2.0 to 2.2 the reference manual section on compiling > to tree-il replaced `begin' with `seq'.  Is `begin' going to be deprecated? It's not merely deprecated, is no longer part of tree-il in 2.2. However, 'parse-tree-il' still handles 'begin', a

Re: (n-for-each-par-map 16 store download (reverse (iota (max-id))))) crash

Hi, Amirouche Boubekki writes: > On 2018-07-05 20:30, Mark H Weaver wrote: >> Amirouche Boubekki writes: >> >>> (define (store pair) >>> (if (null? pair) >>> (format #t "X\n") >>> (let ((port (open-file "hn.scm&q

Re: (n-for-each-par-map 16 store download (reverse (iota (max-id))))) crash

Hi, Amirouche Boubekki writes: > I have a program that try to download hackernews locally. > > What it does is simple, it fetch the max identifier and > http-get each json value starting with the most recent > item. I use n-for-each-par-map with 16 threads I have > 8 cores. > > Here is the full

Re: A Pango attribute deallocated twice

Hi, Tommi Höynälänmaa writes: > The reason of the bug is that the attribute argument to > pango_attr_list_insert has been declared caller owned. I changed > g-wrap so that WCT arguments can be callee owned and I modified > guile-gnome2 so that the second argument of pango_attr_list_insert is > de

Re: How to record source properties for all symbols?

Hi, Fis Trivial writes: > Mark H Weaver writes: > >> The problem is that there's no place to store the source information for >> symbols in the standard S-expression representation. >> >> The principal defining characteristic of symbols -- that "two s

Re: A Pango attribute deallocated twice

Hi, Tommi Höynälänmaa writes: > A Pango attribute gets deallocated twice in program calc-9.scm causing > the program to crash. The Scheme code calc-9.scm is generated from the > Theme-D program calc-9.thp. [...] > IMHO the variable attrlist should not be deallocated at all in the > position wh

Re: How to record source properties for all symbols?

Hi, Fis Trivial writes: > Can you give me some guidance for how to achieve the goal(record all > source information for every symbol). If it's theoretically impossible > or hard to achieve, can you give me some inside why and advises for > making best effort? I intend to help, so pointers to inte

Re: A problem with licenses

Tommi Höynälänmaa writes: > I have published some guile-based software under GNU GPL and > LGPL. However, when I open the Debian packages with Ubuntu Software > Installation (18.04) the application claims that the software is > proprietary. How can I fix this? I don't know, it depends on how tha

Re: About seq in Tree-IL

Hi, Tommi Höynälänmaa writes: > I use Tree-IL as an intermediate language for my own programming > language Theme-D and the generated Tree-IL files contain a huge nested > seq expression. Could we allow multiple toplevel expressions in a > Tree-IL file or have the Tree-IL begin expression back?

Re: German translation of R5RS

Hi Florian, "pelzflorian (Florian Pelz)" writes: > Please accept my patches adding a German language info file for R5RS > and fixing some small errors in English R5RS. I believe the patches > to be reasonably correct. I very much appreciate this enormous amount of work that you've done! My pri

Bogus range calculations for bitwise operations in Guile 2.2

Hi Andy, While investigating , I've found several mistakes in the range calculations for bitwise operations in (language cps types). As a result, 'logand', 'logsub', 'logior' and 'logxor' would sometimes generate bad code. Andy Wingo writes: > wingo pushed a commit

Re: tracepoints/breakpoints and native compilation

Hi Andy, Andy Wingo writes: > A design question for everyone. I am wondering how to support > breakpoints, tracepoints, and the like in a Guile with native-code > compilation. If you are not familiar with what Guile does currently, > see: > > https://www.gnu.org/software/guile/manual/html_no

Re: Performance impact of top level definitions

Hi Brian, Brian writes: > Today I found that top level defines have a significant performance > impact on Guile (2.2.3). The following program takes about 108 seconds > to complete on my ThinkPad (an i5-5200U with Arch Linux): [...] > By simply wrapping that code in a lambda the program finished

Re: [PATCH] Recognize RISC-V compilation targets.

Hi Shea, sorry for the delay. Shea Levy writes: > * module/system/base/target.scm (cpu-endianness): Add case for "riscv" > variants. Applied in commit 08bb4628369cf3efe7c96a32919705c41a9ed9e9 of the stable-2.2 branch, so it will be included in Guile-2.2.4. Thank you for working on RISC-V. That

Re: Thread 1 "guile" received signal SIGPWR, Power fail/restart.

Amirouche Boubekki writes: > I have a guile crash that I can reproduce all the time so far that says: > > Thread 1 "guile" received signal SIGPWR, Power fail/restart. SIGPWR is used internally by libgc. If I recall correctly, it's done to suspend all threads within their signal handlers befor

  1   2   3   4   5   6   7   8   9   10   >