On Wed, May 22, 2024 at 11:33:08AM -0700, Ivan Raikov wrote:
> Hello Peter,
>
> Thanks a lot for the patch! Overall it looks ok, but it has been quite
> a while since I have had to deal with UTF-8 at this level of detail,
> so I don't really understand all the bitwise operations and range
>
On Wed, May 22, 2024 at 02:42:38PM +0200, Peter Bex wrote:
> Attached are two patches, one which has this bigger improvement, and
> another which is a minor improvement which translates to shaving about
> a second of runtime off your program (at least on my machine).
The minor patch was
ation \n") #f ) ; if done ) ; if and ) ; end let*)
> (let ( [n (- (expt 2 257) 1)] [u 2] [v 11] [c 7] [iter 1] [prod 1] )
> (display "factor n = ") (display n) (newline) (time (rho n u v c iter
> prod)))
> ;;;
On Wed, May 15, 2024 at 02:44:07PM +0200, Peter Bex wrote:
> Unfortunately, it also means we must now choose to reject certain URIs
> (at least in uri-common) by raising an exception instead of allowing them
> to be decoded. These are for invalid UTF-8 encoded characters, either
> bec
t with invalid encodings"
+ (for-each (lambda (p)
+ (test-error p (uri-decode-string p)))
+error-decode-cases))
+
+
(define normalize-case-cases
'(("http://exa%2fmple/FOO%2fbar; "http://exa%2Fmple/FOO%2Fbar;)
("http://EXA%2fMPLE/FOO%2fbar; "http://exa%2Fmple/FOO%2Fbar;)
Inde
On Mon, Apr 29, 2024 at 12:10:14PM +0200, felix.winkelm...@bevuta.com wrote:
> > Another attempt at fixing #1835, hopefully this time for good.
> >
> > Adds a +1 to each paramter string's length, to permit starting to compare
> > at end of string, and corresponding tests.
> >
> > The errors I
nce
this has been applied.
Also, there are a few fixes related to utf8-mode, so maybe these help
with the UTF-8 branch.
Cheers,
Peter
>From 411dcdd39fde172f414e29a216ed413a4758 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Tue, 23 Apr 2024 08:26:07 +0200
Subject: [PATCH] Bump i
On Tue, Jan 16, 2024 at 06:09:33PM +0100, felix.winkelm...@bevuta.com wrote:
> This patch addresses the problem reported recently my Mario, regarding
> failing compilation of http-client.
>
> The problem was that compiler-syntax definitions changed the "override"
> status and disabled the
On Tue, Nov 14, 2023 at 01:22:59PM +0100, felix.winkelm...@bevuta.com wrote:
> Yes, this is admittedly all a bit ugly. Please find attached 2 patches:
> the first addresses the endless expansion loop caused by our recent change
> in ##sys#canonicalize-body. The second patch is a new version of the
On Sun, Nov 12, 2023 at 01:45:06PM +0100, felix.winkelm...@bevuta.com wrote:
> See commit message.
Nice to make some progress on this!
However, I tested the example given in the ticket:
(define begin -)
(begin 0 1) => 1 ;; expected: -1
This still evaluates to 1.
Cheers,
Peter
On Sun, Nov 12, 2023 at 12:45:49PM +0100, felix.winkelm...@bevuta.com wrote:
> The attached patch addresses an endless expander loop while compiling
> the transducers egg. The egg uses unconvential (and only slightly legal)
> alias identifiers that confuse the expander, combined with a recent
>
On Wed, Nov 08, 2023 at 02:59:17PM +0100, felix.winkelm...@bevuta.com wrote:
> Attached is a patch to address #1492.
Applied. Do we want to turn this into an error for CHICKEN 6?
Warnings have a tendency of just scrolling by and getting lost in the
noise of compiler output.
OTOH, making it an
On Wed, Nov 08, 2023 at 12:34:23PM +0100, felix.winkelm...@bevuta.com wrote:
> See commit message.
Shouldn't we modify the test instead of dropping it?
Something like this:
(module m3 ()
(import (rename scheme (define s:define)))
(import (only (chicken base) assert))
(define-syntax define
On Tue, Oct 10, 2023 at 08:14:54AM +0200, Peter Bex wrote:
> After some more thought on this, I think you convinced me.
> Let's go with the original export/rename patch, unless anyone objects.
A week has passed with no objections. I've pushed the original patch.
Cheers,
Peter
signatu
On Mon, Oct 09, 2023 at 05:01:47PM +0200, felix.winkelm...@bevuta.com wrote:
> The export/rename localizes the functionality and doesn't
> require changes to existing code. The precedent of the syntax: and
> interface: never was a particularly good one (we should have used separate
> export forms
On Tue, Oct 03, 2023 at 12:51:57PM +0200, felix.winkelm...@bevuta.com wrote:
> Ok, I find attached a variant, both more ugly in interface and
> implementation, since ##core#module and functor do not yet allow
> renamings to be handled. Also, "define-interface" has no notion
> of this, so
On Mon, Oct 02, 2023 at 06:31:44PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch adds a new special form to explicitly export renamed bindings
> from a module:
>
> (export/rename (OLD NEW) ...)
Why not add it to the regular "export" form? It's already extendable,
as it has syntax:
On Tue, Sep 26, 2023 at 12:33:43PM +0300, elf wrote:
> It certainly shouldn't be *, nor should it be an error... technically an
> empty union should be a null set, which would correspond to either a
> non-extant type or to no return/value at all...
We've discussed this on IRC. Such a null type
On Wed, Aug 16, 2023 at 05:25:45PM +0200, felix.winkelm...@bevuta.com wrote:
> > Why are install-path and repo-path in chicken-install.scm still using
> > destination-repository instead of effective-destination-repository?
> > Those are the only places that still use it, aside from one in
> >
On Fri, Jul 21, 2023 at 04:12:52PM +0200, felix.winkelm...@bevuta.com wrote:
> Indeed - sorry about that, here an improved version.
Sorry for the delay, but I finally had a bit of time to look into this
more seriously, but honestly I'm confused by all the parameters.
Why are install-path and
On Thu, Jul 27, 2023 at 12:30:46PM +0200, Peter Bex wrote:
> 1) There's no (efficient) way to know if an object is a finalizable one.
>We need this because we can't simply clear *all* the objects inside
>a finalizable object that aren't referenced elsewhere, because we do
>
On Wed, Jul 26, 2023 at 04:45:53PM +0100, Andy Bennett wrote:
> So how can we finalise a circular list of objects all of which have
> finalisers and still maintain atomicity?
>
> The docs say the order is "undefined".
> It seems that the best way to finalise this structure is to explicitly break
On Fri, Jul 21, 2023 at 03:54:41PM +0200, felix.winkelm...@bevuta.com wrote:
> diff --git a/egg-compile.scm b/egg-compile.scm
> index 99a94fe8..b14535da 100644
> --- a/egg-compile.scm
> +++ b/egg-compile.scm
> @@ -412,7 +420,7 @@
> (define (compile-common info walk)
>(case (car info)
On Fri, Jul 07, 2023 at 10:43:29AM +0200, felix.winkelm...@bevuta.com wrote:
> Here another attempt at a finalizer API, allowing adding
> finalized objects to an existing finalizer after it was
> created.
Thanks, I've pushed both this and the srfi 18 changes.
Should we tag a new srfi-18 release?
Hi all,
Here's a patch to change the name of the read/source-info we export from
chicken.syntax. This avoids a problem we've been seeing on the
Salmonella machines with hanging processes.
Cheers,
Peter
From 520c12c7642448af2bc1c6e0a1790794d06dc2d4 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date
On Mon, Jul 10, 2023 at 09:28:19PM +0200, felix.winkelm...@bevuta.com wrote:
> After thinking some more about this, I realize that your approach
> (clearing weak ref's to finalized data) is the right thing, since
> any other behaviour in the presence of multithreading leads to
> disaster.
Thank
On Fri, Jul 07, 2023 at 11:23:17PM +0200, felix.winkelm...@bevuta.com wrote:
> I'm not very comfortable with this change. This feels like trading in
> one inconsistency (weak refs being cleared for a potentially non-dead
> object) for another (potentially inconsistent ties of GC-controlled
>
eafdcca8b609c443d717e67 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Fri, 7 Jul 2023 11:07:43 +0200
Subject: [PATCH 1/2] Skip weak locatives that were already invalidated
This avoids a NULL pointer dereference
---
runtime.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/runtime.c b/runt
On Thu, Jul 06, 2023 at 02:51:43PM +0200, felix.winkelm...@bevuta.com wrote:
> That is indeed a shortcoming of the API. I must say that I'm not
> too keen on the "guardian" approach, though, or your suggested hacky
> workaround. There would be too many meanings attached to the
> argument for the
On Wed, Jul 05, 2023 at 03:28:54PM +0200, felix.winkelm...@bevuta.com wrote:
> The first patch provides the event-queue mechanism and cleans up the
> scheduler a bit (hiding internal variables while also exposing ##sys#...
> procedures to access them). This also defines hooks that a threading
>
On Wed, Jul 05, 2023 at 07:27:43PM +0200, felix.winkelm...@bevuta.com wrote:
> Reported by "acdw": make "tail?" more robust. Also generalizes
> it to accept all types of data, remove unneeded fast path expecting
> proper list argument.
Thanks, pushed!
Cheers,
Peter
signature.asc
Description:
Hi there,
The attached patch fixes a small but important oversight in
get-call-chain. With this patch, the "trace" egg's tests pass again.
Cheers,
Peter
From 7e20f8dc5310ee8fb41522bff062783b224b07f3 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Fri, 30 Jun 2023 09:42:48 +0200
Subje
noticed there's also an error in the "trace" egg. This probably has
something to do with the changes in the call chain. Not sure how, but
I'll investigate.
Cheers,
Peter
From ed691a470bd45bf1ecb9a8d8f53fdfbe4d8c952a Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Fri, 30 Jun 2023 09:0
resentation, I think this change is
better left for CHICKEN 6.
Cheers,
Peter
From 8f753a2d031a3c23198c397223f55ce3ae7ec087 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Tue, 27 Jun 2023 08:13:59 +0200
Subject: [PATCH] Replace locative table with simpler "weak chain" solution
Ins
On Sun, Jun 25, 2023 at 08:06:01AM +0200, felix.winkelm...@bevuta.com wrote:
> Hi!
>
> Attached a patch to fix some problems with the newly introduced
> extension to SRFI-4 vector read syntax. "Siiky" pointed out a bogus
> empty string comparison and further testing showed that empty strings
>
it as an additional argument to emit-trace-info.
Patch has also been pushed to the line-numbers-in-csi branch.
Cheers,
Peter
From df10eb66dc22a1538bdab4ceafd3f15812c18842 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Sun, 25 Jun 2023 10:22:01 +0200
Subject: [PATCH] Fetch line number from info
On Wed, Jun 07, 2023 at 09:12:51PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch allows strings and chars in homogenous number vectors,
> as suggested by klm at the meetup.
Code is a bit hairy, but seems to work. Pushed!
Cheers,
Peter
signature.asc
Description: PGP signature
ew more changes and I'm not sure of
the benefits.
Cheers,
Peter
From 1330e7d252eac583d6c0bbabc4917a99a1437135 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Tue, 20 Jun 2023 15:14:53 +0200
Subject: [PATCH 1/6] Move line number database accessors from support.scm to
expand.scm
Because support.scm i
On Mon, Jun 19, 2023 at 01:38:13PM +0200, felix.winkelm...@bevuta.com wrote:
> Attached patch fixes a segfault when trying to describe a brokwn weak
> ptr. I also added a clause in the case construct to dispatch on a
> described value to catch unknown immediate values instead of crashing
> in the
On Mon, Jun 05, 2023 at 08:12:01PM +0200, felix.winkelm...@bevuta.com wrote:
> Thanks a lot, Christian, much obliged.
Indeed, thanks Christian!
> I have combined the two patches and amended the result slightly (wrappers in
> runtime.c for all trigonometric functions were not calling the
>
On Sat, Jun 03, 2023 at 11:12:40PM +0200, Peter Bex wrote:
> Attached are 5 patches to add the weak pair support. I've also pushed
> this to the git repo under the "user-facing-weak-pairs" branch.
Attached are two more patches that together wrap up the weak pairs
support. The
On Sat, Jun 03, 2023 at 11:12:40PM +0200, Peter Bex wrote:
> Attached are 5 patches to add the weak pair support. I've also pushed
> this to the git repo under the "user-facing-weak-pairs" branch.
I've pushed two more patches, attached here as well.
The first one implements th
On Tue, Jun 06, 2023 at 07:46:10PM +0200, felix.winkelm...@bevuta.com wrote:
> > Do we even want to make a 5.4 release at all?
>
> I would suggest to add this for 5.4, for the reasons you
> state. I also would be for making at least one minor release
> before C6, as I doubt that we will get UTF
On Sat, Jun 03, 2023 at 11:12:40PM +0200, Peter Bex wrote:
> Dear hackers,
>
> At the Village CHICKENs event, I gave a presentation about how we could
> add "proper" support for weak pairs, so that they can be exposed to the
> user.
PPS: When writing tests for weak
On Sat, Jun 03, 2023 at 11:12:40PM +0200, Peter Bex wrote:
> Dear hackers,
>
> At the Village CHICKENs event, I gave a presentation about how we could
> add "proper" support for weak pairs, so that they can be exposed to the
> user. Right now we have half-baked support f
it should be easy to understand even if you haven't
seen my talk at the Village CHICKEN event.
Cheers,
Peter
From 1d477b2857ec3f01c5367dadc5725b85e7b53799 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Sat, 3 Jun 2023 11:20:40 +0200
Subject: [PATCH 1/5] Replace special-casing of weak symbol GC wi
On Tue, Mar 14, 2023 at 08:43:52AM +0100, Peter Bex wrote:
> On Tue, Mar 14, 2023 at 08:40:18AM +0100, felix.winkelm...@bevuta.com wrote:
> > Backwards compatibility is from now on fucked anyway, so let's
> > try to find somethin simple and sensible.
>
> Then we should
On Tue, Mar 14, 2023 at 02:48:28PM +0100, Mario Domenech Goulart wrote:
What should the behavior of executables be in case they are compiled
> with the runtime options parser disabled (e.g.,
> -disable-runtime-options, as per Felix' previous patch)?
Assuming we go with the decision to process
On Tue, Mar 14, 2023 at 08:40:18AM +0100, felix.winkelm...@bevuta.com wrote:
> > Of course. In fact, I think it would make more sense to simply tell the
> > runtime options parser to stop after the first non-"-:"-prefixed
> > argument. That makes runtime argument stuffing harder and allows it
>
On Tue, Mar 14, 2023 at 08:39:22AM +0200, Lassi Kortela wrote:
> Is there any reason -: runtime options need to be recognized beyond the
> first argument? Gambit also uses the -: syntax, and it does not.
Making it compatible might be nice, but involves a change in how these
options are parsed -
On Mon, Mar 13, 2023 at 09:35:53PM +0100, felix.winkelm...@bevuta.com wrote:
> > In other words, "./my-program -:a100 -- foo" is seen as '("--" "foo")
> > when you ask for (command-line-arguments), while the intention probably
> > was '("foo").
>
> Actually not. Currently "--" is not specially
On Mon, Mar 13, 2023 at 10:37:30AM +0100, felix.winkelm...@bevuta.com wrote:
> Another problem with run-time option processing pointed out by
> florz. This allows passing arguments that look like run-time
> options, when preceded by "--".
This needs more thought - simply adding "--" to stop it
On Sun, Mar 12, 2023 at 06:04:49PM +0100, felix.winkelm...@bevuta.com wrote:
> As rightly pointed out by florz and others, the "b" (break on
> repl) offers a potential security vulnerability by allowing
> code from stdin to be interpreted. This patch simply removes
> the option, as it doesn't seem
On Sun, Oct 30, 2022 at 02:47:47PM +0100, felix.winkelm...@bevuta.com wrote:
> See #1753, as reported by Kon. This will bust egg caches, but should otherwise
> not cause any incompatibilities.
Pushed, thanks Felix.
However, I noticed it would still just install an egg I had previously
On Wed, Nov 02, 2022 at 10:24:13AM +0100, felix.winkelm...@bevuta.com wrote:
> The attached patch was contributed by Vassilij. See #1800.
Thanks guys, pushed the updated version of this we discussed elsewhere.
Cheers,
Peter
signature.asc
Description: PGP signature
ve nothing to do with this - just
the platform was still being passed in to "filelist" and was *not* being
passed in to print-build-command. I've fixed these already and pushed
them as trivial patches.
Cheers,
Peter
From 651f70a66ed2ab3e70334466ae8a93b57ffbaa10 Mon Sep 17 00:00:00 2001
From: P
"share" files (data files)
Cheers,
Peter
From e8341cca08c43e8bac1c5d08aaac670f5c37d211 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Mon, 31 Oct 2022 13:06:26 +0100
Subject: [PATCH] Do not double call normalize-destination on share dir
In install-random-files, don't call normalize-
istencies here.
How about the attached patch instead? It may be a little bit
trickier to read (but not by much), but should eliminate the
problem entirely for chicken-do calls.
Cheers,
Peter
From 730c74994a5feb96ef5d1d7ac2afdefbad65db7a Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Mon, 31 Oct 2022
On Sun, Oct 30, 2022 at 02:48:27PM +0100, felix.winkelm...@bevuta.com wrote:
> in egg-compile.scm, as suggested by Peter.
Thanks, pushed.
Cheers,
Peter
signature.asc
Description: PGP signature
On Fri, Oct 28, 2022 at 05:47:22PM +1300, Evan Hanson wrote:
> Applied!
>
> Lots of tickets closed lately, very cool.
Indeed. I've taken the liberty of adding these two changes to the NEWS
file. Even though they're relatively minor, they correspond to
tickets/bug reports by users, so it's
On Tue, Oct 25, 2022 at 12:09:55PM +0200, Peter Bex wrote:
> Also, we forgot to look at Salmonella or we'd noticed:
> http://salmonella-linux-x86-64.call-cc.org/master/gcc/linux/x86-64/2022/10/24/yesterday-diff/
So above, that's "-151" for succesfull installation, i.e. we broke
On Mon, Oct 24, 2022 at 05:23:24PM +0200, felix.winkelm...@bevuta.com wrote:
> As reported by Kon, our previous "fix" for shell argument quoting
> exposed another bug, this is an attempt to improve on that.
Thanks, pushed.
Also, we forgot to look at Salmonella or we'd noticed:
On Fri, Oct 21, 2022 at 03:58:42PM +0200, felix.winkelm...@bevuta.com wrote:
> This stuff is obscure and, as described in #1774, packaging/"deploying"
> applications is something
> that should be left to application developers.
Agreed, patch pushed.
Cheers,
Peter
signature.asc
Description:
On Mon, Oct 24, 2022 at 11:23:09AM +0200, felix.winkelm...@bevuta.com wrote:
> The attached patch addresses the broken semantics of -prelude/-postlude
> in the compiler driver, as reported by sjamaan.
Thanks, pushed!
I wonder how this got so broken.
Cheers,
Peter
signature.asc
Description:
On Sun, Oct 23, 2022 at 12:36:20PM +0200, felix.winkelm...@bevuta.com wrote:
> > On Fri, Oct 21, 2022 at 04:36:58PM +0200, felix.winkelm...@bevuta.com wrote:
> > > See #1302.
> >
> > Why do we even attempt to detect whether to quote? That looks a bit
> > brittle to me. It should be simpler to
On Fri, Oct 21, 2022 at 04:36:58PM +0200, felix.winkelm...@bevuta.com wrote:
> See #1302.
Why do we even attempt to detect whether to quote? That looks a bit
brittle to me. It should be simpler to just always quote (e.g. using "qs"),
like we do in other places, for example in chicken-install,
On Fri, Oct 21, 2022 at 11:26:05AM +0200, felix.winkelm...@bevuta.com wrote:
> See #1809, as suggested by Zipheir.
Thanks, pushed! I also took the liberty of adding Zipheir to the
acknowledgments and adding the change to the NEWS file.
> +(define (string-trim str)
> + (let loop ((front
On Tue, Oct 12, 2021 at 12:13:17PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch changes chicken-do to emit a warning when a dependency is missing,
> but lets it still continue. That way missing dependencies in egg files can at
> least
> not break the build.
Why not break the build
On Thu, May 19, 2022 at 12:03:16PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch addresses the unnecessary interning in char-comparison
> procedures.
Thanks, pushed!
Cheers,
Peter
signature.asc
Description: PGP signature
On Sat, Mar 26, 2022 at 05:59:24PM +0100, felix.winkelm...@bevuta.com wrote:
> Hi!
>
> Attached a patch to address the issue reported by Claude Marinier.
> I tried to understand what the expected behaviour of umask should
> be, but in the end I just dropped the whole test, since I don't
>
On Thu, May 19, 2022 at 02:34:09PM +0200, felix.winkelm...@bevuta.com wrote:
> Oh boy... I should have looked at that a bit more seriously, Sorry about that.
No worries!
> Attached a new patch.
Thanks, pushed!
Cheers,
Peter
signature.asc
Description: PGP signature
On Thu, May 19, 2022 at 12:01:43PM +0200, felix.winkelm...@bevuta.com wrote:
> These tests were contributed by Christian Himpe.
> +;;; Tests contributed by Christian Himpe:
> +
> +;; dummy testee
> +(define (fp*+ a b c)
> + (+ (* a b) c))
> +
IIUC that means these tests aren't actually
On Sun, Feb 20, 2022 at 01:58:31PM +0100, felix.winkelm...@bevuta.com wrote:
> > Hi all,
> >
> > First time contributing to CHICKEN itself. Is this all?
> >
>
> Basically, yes. Attached is a signed off copy of the patch, now
> we wait for some other core developer to apply it...
Sorry for the
On Sat, Jan 29, 2022 at 12:08:17PM +0100, Sören Tempel wrote:
> I don't think there is a semi-portable way of doing this, or at least I
> am personally not aware of one. However, maybe a Makefile configuration
> variable could be introduced specifically for creating CHICKEN Scheme
> packages for a
On Sun, Jan 23, 2022 at 12:54:58PM +0100, Sören Tempel wrote:
> I recently started working on Alpine packages for Scheme software which
> I compiled with CHICKEN. While doing so, I noticed that csc(1)
> unconditionally adds $(LIBDIR) as an rpath entry by adding
> -Wl,-rpath=$(LIBDIR) to the linker
and defined, but this no longer seems to be in
use. The attached patch removes the obsolete #ifdef HAVE_CONFIG_H block
from runtime.c
Cheers,
Peter
From dba340c1fe1b3e966e69ee51bb951b121e84079a Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Wed, 20 Oct 2021 09:38:45 +0200
Subject: [PATCH] Remove
On Tue, Oct 12, 2021 at 12:18:52PM +0200, felix.winkelm...@bevuta.com wrote:
> See attached patch. This change is not intended for the current RC.
Thanks, applied. I changed 5.4.0 to 5.3.1 in the NEWS file, as this
change would appear in the first snapshot we make (assuming we will
make one
On Tue, Sep 28, 2021 at 04:52:26PM +0200, felix.winkelm...@bevuta.com wrote:
> Hi!
>
> The attached patch should fix the issue of builtin module ids appearing in
> generated
> ..link files.
Thanks, pushed!
Cheers,
Peter
signature.asc
Description: PGP signature
.
Cheers,
Peter
From da9f177e085c8c49efe6cbda0b90939f7f1e759a Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Fri, 24 Sep 2021 08:25:07 +0200
Subject: [PATCH] Add checks to current user/group id setters in (chicken
process-context posix)
Fixes #1787
---
NEWS| 9 +
manual
69bff630d1 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Thu, 2 Sep 2021 08:03:39 +0200
Subject: [PATCH 1/2] Ensure all ports are closed in tests when deleting the
file
Under Windows, read-lines-test.scm and posix-tests.scm would
fail with "permission denied" upon deletion of the out
On Mon, Aug 30, 2021 at 08:10:46PM +0300, elf wrote:
> I do use Windows regularly and am looking to improve chicken support for it.
Hi Elf,
Cool to hear. What are your thoughts on the current situation? Which
flavour of Windows build should we keep and which should we drop (if any)?
What about
rove support on Windows.
That's a catch-22 though: in order to get that help, we need CHICKEN
in a useful-enough state that people can use it on Windows. And in
general, out of the total set of users, only a small subset will
actually contribute.
Cheers,
Peter
From 1edd51e77982ebce33b165e481da8d
On Wed, Aug 25, 2021 at 09:29:31PM +0300, Jani Hakala wrote:
>
> Hi,
>
> This patch seems to fix the problem with chicken-install when
>
> chicken-install -defaults ./setup.defaults -update-db
>
> appears to hang when installing chicken.
I've done some investigation. First off, Windows
On Thu, Aug 19, 2021 at 01:58:48PM +0200, Peter Bex wrote:
> PS: aren't all the register-primitive-module invocations for srfis wrong,
> in that they register a module under a similarly named unit, but there
> is no such unit library (in any of these cases)?
I thought about it
unit to be linked in.
Cheers,
Peter
From 86530c17b873c5063ff56275ea4d8e4af29d123f Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Thu, 19 Aug 2021 13:45:29 +0200
Subject: [PATCH] Also export setter and getter-with-setter from builtin
srfi-17 module
Thanks to Lassi Kortela for t
On Fri, Aug 06, 2021 at 10:22:42PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch changes TARGET_SHARE_HOME to also include the "chicken" suffix,
> so it should be identical to INSTALL_SHARE_HOME in normal situations (when
> not cross-compiling). This also addresses the installation
Hi all,
Evan just closed the last ticket in our roadmap for 5.3
(https://bugs.call-cc.org/roadmap). So I think now is a good
time to start the (pre)release process.
However, there are a few questions remaining regarding uninstallation
of files and the file tree in the README. Should we wait
On Tue, Aug 03, 2021 at 08:07:33PM +0300, Lassi Kortela wrote:
> README shows the following layout for files installed under "share":
>
> `-- share
> |-- chicken
> | |-- doc
> | | |-- LICENSE
> | | |-- README
> | | |--
On Tue, Aug 03, 2021 at 07:06:23PM +0300, Lassi Kortela wrote:
> Patch attached to fix the problem.
Thanks, pushed!
> Even with this patch applied, `make uninstall` still leaves behind some
> empty directories:
>
> |-- bin
> |-- include
> | `-- chicken
> |-- lib
> | `-- chicken
> `-- share
And now with reexport-m9.scm and reexport-m10.scm
From ab6b7e798151e8af2d987e91acdf86f98f0251f4 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Sun, 1 Aug 2021 15:35:44 +0200
Subject: [PATCH] Add regression test for #1771
This bug was fixed by the fix for #1772, but this was supposed to only
084b189e6adaf4809649ee44e72bec0c8115b0cd Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Sun, 1 Aug 2021 15:35:44 +0200
Subject: [PATCH] Add regression test for #1771
This bug was fixed by the fix for #1772, but this was supposed to only
be a performance improvement, so the fix was "accidental" (and,
a
On Sat, Jul 31, 2021 at 04:05:52PM +1200, Evan Hanson wrote:
> I was wondering whether there are any implications in changing the order
> of the `sexports` field of the module, now that we're putting all
> "normal" syntax exports before any re-exported ones. However, after a
> bit of digging, I
Hi all,
Attached is a straightforward fix for #1772. I put it on the
milestone 5.4, but since it's such a simple fix, I think we
could include it in 5.3 anyway.
Cheers,
Peter
From 70e45fe529d51421fbeea8828dc1704e3a821d40 Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Thu, 22 Jul 2021 13:22:00
Sep 17 00:00:00 2001
From: Peter Bex
Date: Wed, 21 Jul 2021 11:35:18 +0200
Subject: [PATCH] Remove severely outdated README section on compatibility
This mentioned only the upgrade from 3 to 4, and had nothing
about 4 to 5 anyway. Better to remove it completely to avoid
confusion.
---
README | 13
. Likewise, quotes inside
paths are illegal, therefore no quotes should be used inside PATH.
It appears that the Windows shell cannot deal with quoting inside an
argument, only when quotes surround the argument. This is not the case
on Unix environments at all.
Closes #1727
Signed-off-by: Peter Bex
work if we keep it referring to only local macros,
and I think we shouldn't mess too much with the environments
where that's not needed, so I think it's fine.
Cheers,
Peter
From 96827b77554e8b56838b0e47363326011b6e Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Wed, 14 Jul 2021 12:18:56 +02
Hi all,
Here's one more patch to bring Irregex completely up to date with the
just released 0.9.10 version. It fixes an issue where "bol" would
overlap with newline characters in a weird way.
Cheers,
Peter
From efe932f4fa7afbc56865d33edfbf6836c34ce919 Mon Sep 17 00:00:00 2001
From:
On Thu, Jul 01, 2021 at 10:44:22PM +0200, felix.winkelm...@bevuta.com wrote:
> See patch, suggested by jcroisant on #chicken. Since -lxxx may
> be ambiguous, not all cases may be caught, but it can still be helpful to new
> users.
Thanks, applied. The patch has some weird indentation and also
On Mon, Jul 05, 2021 at 11:45:36AM +0200, Peter Bex wrote:
> Hi there,
>
> The attached patch is a port of the most recent commit in the irregex
> repository, which fixes this upstream ticket:
> https://github.com/ashinn/irregex/issues/27
And here is another patch to fix a differe
Hi there,
The attached patch is a port of the most recent commit in the irregex
repository, which fixes this upstream ticket:
https://github.com/ashinn/irregex/issues/27
Cheers,
Peter
From b552052f4085e84d662f70bb76cb4abf41ab25bc Mon Sep 17 00:00:00 2001
From: Peter Bex
Date: Mon, 5 Jul 2021 11
1 - 100 of 1541 matches
Mail list logo
