Re: Non-blocking web server

On Sun, Mar 24, 2024 at 03:41:32PM -0400, Ryan Raymond wrote: > Hello, all. > I was able to build a non-blocking web-server using network sockets. > However, the existing guile web/server.scm implementation is > single-threaded and therefore blocking [...] How does "single-threaded" imply

Re: How to abort a read from a socket after some time?

to returning an ‘EINTR’ error from that call). Based on that my expectation was to get EINTR. But since the syscall seems to be restarted even without the SA_RESTART, what exactly does this flag do then? Thank you, Tomas Volf -- There are only two hard things in Computer

Re: Problems with running Network Socket Examples

On Sun, Nov 26, 2023 at 09:59:58PM +0100, Erik Grun wrote: > Hello, Guile-Devel, > > I just can't get the Network Socket Examples[1] to work. I am using Guile > 3.0.7. > > An obvious mistake seems to be, that the docs use different ports for client > (80) and server (2904), but even if I use the

[PATCH v2] Add more detailed instructions into the HACKING file.

Until now, the ./meta/guile was not mentioned anywhere, and therefore it was not obvious how to run the locally compiled Guile without installing it. While modifying the file, I took the liberty to also mention a bit about compiling Guile using Guix. Finally, the header lines where cleaned up,

Re: [PATCH] Add more detailed instructions into the HACKING file.

Thank you for the review. On 2023-12-04 22:06:42 +0100, Maxime Devos wrote: > > > Op 29-11-2023 om 17:40 schreef Tomas Volf: > > +guix shell -D -f guix.scm --pure -- ./configure --enable-mini-gmp > > Also -fexcess-precision=standard (see #49368 / #49659 on debbugs)

[PATCH] Add more detailed instructions into the HACKING file.

Until now, the ./meta/guile was not mentioned anywhere, and therefore it was not obvious how to run the locally compiled Guile without installing it. While modifying the file, I took the liberty to also mention a bit about compiling Guile using Guix. Finally, the header lines where cleaned up,

[PATCH] Add copy-on-write support to scm_copy_file.

On modern file-systems (BTRFS, ZFS) it is possible to copy a file using copy-on-write method. For large files it has the advantage of being much faster and saving disk space (since identical extents are not duplicated). This feature is stable and for example coreutils' `cp' does use it

[PATCH] doc: Fix example in list-transduce example.

While the `.' might be correct from a grammatical point of view (I do not know), it turns the example into invalid scheme code, which is not ideal. New users (like me) might try to copy the whole line and wonder why it does not work (like I did). So delete it. * doc/ref/srfi-modules.texi

[PATCH v3] doc: Extend documentation for (ice-9 match)

Extend the documentation for (ice-9 match) module with explanations of some of the patterns and also provide more examples for them. That should make it more useful for people trying to use the module for the first time just based on the documentation. * doc/ref/match.texi (Pattern Matching):

[semi-OT] Snarfing [was: [PATCH v2] doc: Document SRFI 64.]

On Wed, Nov 22, 2023 at 09:42:49PM +0100, Maxime Devos wrote: [...] > (I assume 'snarfing' is a form of copying here.) Basically yes. Something like "stealing", perhaps because the source isn't aware of the fact that it has got a new use. The term is old UNIX tradition [1]. From there, it

[PATCH v2] doc: Extend documentation for (ice-9 match)

Extend the documentation for (ice-9 match) module with explanations of some of the patterns and also provide more examples for them. That should make it more useful for people trying to use the module for the first time just based on the documentation. * doc/ref/match.texi (Pattern Matching):

Re: [PATCH] doc: Extend documentation for (ice-9 match)

Hello, thanks for the review! My reactions are below. On 2023-09-20 00:57:33 +0200, Maxime Devos wrote: > > > Op 06-09-2023 om 16:06 schreef Tomas Volf: > > Extend the documentation for (ice-9 match) module with explanation of > > some of the patterns and also provide m

[PATCH] doc: Extend documentation for (ice-9 match)

(+) diff --git a/THANKS b/THANKS index aa4877e95..bb07cda83 100644 --- a/THANKS +++ b/THANKS @@ -38,6 +38,7 @@ Contributors since the last release: BT Templeton David Thompson Bake Timmons + Tomas Volf Mark H Weaver Göran Weinholt

Re: (. wtf?)

On Mon, May 08, 2023 at 01:53:31PM +0300, Dmitry Alexandrov wrote: > wrote: > >> it is required for compatibility with elisp > > > > Is it Guile's incompatibility with Emacs Lisp > > As of now, they are compatible in that regard. > > > (no wonder: the first is a Scheme, the second a Lisp: they

Re: (. wtf?)

On Mon, May 08, 2023 at 07:31:11AM +0200, Dr. Arne Babenhauserheide wrote: > > writes: > > > You seem to be somewhat upset, but I don't quite understand what > > your gripe is. > > If I understood it correctly, they interpret the 'wtf? as expressing > "this is a problem that should be changed"

Re: (. wtf?)

On Sun, May 07, 2023 at 09:06:21PM +0300, Dmitry Alexandrov wrote: > On Fri, 05 May 2023 16:35 Ludovic Courtès wrote: > > (call-with-input-string "(. wtf?)" read) > > > > ⇒ wtf? > > > > #Guile #Scheme > > Hey!^W Sorry... > > Dear Guile developer, > > your tweet made me deeply concerned. Is

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 09:21:37AM +0100, Dr. Arne Babenhauserheide wrote: > > writes: > > I'd apply Clarke's Razor:"A sufficiently advanced form of malice > > is not distinguishable from stupidity" > > I love this! Thank you for sharing! I reflected a bit on its genesis. It started while

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 11:49:27AM +0100, Stefan Israelsson Tampe wrote: > [...] Learning how to use ChatGpt to improve > your code quality and productivity is how we should approach it. And the > more experienced you are, the more effective use you will have of it. The stench of Microsoft [1] is

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 10:03:15AM +0100, Mikael Djurfeldt wrote: [...] > > I know very little apart from knowing what deep learning is and having > > skimmed the "Attention is all you need"-paper. That's already more than I do, I think. Thanks for the pointer :) > >

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 09:41:37AM +0100, Mikael Djurfeldt wrote: > On Sat, Mar 18, 2023 at 9:36 AM wrote: [...] > > Perhaps you didn't know, but you are training the model :-) > > > > Unfortunately not. I'm prompting it within its 32000 token (GPT-4) > attention span. Next conversation the

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 09:22:43AM +0100, Mikael Djurfeldt wrote: > BTW, in the bouncing ball example, I find it amazing that I could get an > improvement of the code by complaining: > > But all those SDL_ calls look like C bindings. Please use guile-sdl2 > bindings. > > (It was also quite

Re: GPT-4 knows Guile! :)

On Sat, Mar 18, 2023 at 08:55:03AM +0100, Mikael Djurfeldt wrote: > >1. Install Guile: > > > > > > > csharp > > ^^ > > > > > > sudo apt-get install guile-2.2 > > > > [...] > > > > Did it literally write "csharp"? With some fantasy, I guess it > > is trying to evoke a root shell, but

Re: GPT-4 knows Guile! :)

On Fri, Mar 17, 2023 at 06:25:55PM +0100, Mikael Djurfeldt wrote: > Can you write a Guile Scheme program which displays a bouncing ball? > > As an AI language model, I cannot create a full graphical program directly > within this text-based environment. However, I can provide you with an >

Re: patch for mmap and friends

On Sat, Jan 14, 2023 at 04:18:58PM +0100, Maxime Devos wrote: [...] > (While it is recommended for Scheme code to keep a reference to the port to > manually close afterwards, to free resources faster than waiting for GC, it > is not actually required.) Oh, oh. I've got a little anecdote to

Re: Guile VM interpreter in GraalVM Truffle framework

On Fri, Dec 23, 2022 at 09:51:11PM +0100, Maxime Devos wrote: > On 23-12-2022 18:06, Arvydas Silanskas wrote: > > Good day, > > > > I have aspirations to run scheme on graalvm's truffle framework. And on > > superficial research, it seems implementing a Guile VM bytecode > > interpreter could be

Re: help needed with stderr redirection

On Sat, Oct 22, 2022 at 01:29:05AM +0200, Csepp wrote: > I have this short snippet of code for a Guix related utility script and > for the love of the Glowcloud it does not want to work. I want to > filter stderr for certain lines and they are not being redirected. When > running the full script

Re: avoid character encoding/escaping in sxml->xml or htmlprag's sxml->html

On Sun, Aug 21, 2022 at 12:16:54PM +0200, Maxime Devos wrote: > On 21-08-2022 02:05, Aleix Conchillo Flaqué wrote: > > > According to the spec, embedding inline content in the

Re: avoid character encoding/escaping in sxml->xml or htmlprag's sxml->html

On Sat, Aug 20, 2022 at 05:05:22PM -0700, Aleix Conchillo Flaqué wrote: > Hi Maxime, > > On Sat, Aug 20, 2022 at 2:48 PM Maxime Devos wrote: > > > > The GuileScript looks nice, for interested readers, see < > https://github.com/aconchillo/guilescript> > > > > On 20-08-2022 21:59, Aleix Conchillo

Re: Tom Lord passing

On Tue, Jul 19, 2022 at 04:31:41PM -0700, Andy Tai wrote: > Thomas Lord was an early (or the first?) maintainer of guile > > from https://berkeleydailyplanet.com/issue/2022-06-26/article/49837 > > Obituaries > > Thomas Lord > 1966-2022 [...] Thanks for the reminder. I know I'll miss him.

Re: Heads-up: LilyPond now running Guile 2.2

On Fri, Mar 18, 2022 at 12:17:56AM +0100, Jean Abou Samra wrote: > For your information: > > https://gitlab.com/lilypond/lilypond/-/merge_requests/1250 You rock! Seriously Thanks. Cheers -- t signature.asc Description: PGP signature

Re: GNU Guile 3.0.8 released

it, and the To: header field looks innocent enough: To: guile-u...@gnu.org, guile-sour...@gnu.org, guile-devel@gnu.org, info-...@gnu.org Here are the more envelope-ish headers: From guile-devel-bounces+tomas=tuxteam...@gnu.org Fri Feb 11 08:48:40 2022 Return-path: Envelope-to: to...@tuxteam.de

Re: Fwd: [Patch] definitions in when, unless, do as well as in cond- and case-clauses

On Sun, Feb 06, 2022 at 09:28:15PM +0100, Maxime Devos wrote: > Stefan Israelsson Tampe schreef op zo 06-02-2022 om 21:13 [+0100]: > > Hmm just why conditionals use begin and not let, > > I'd assume the reason is that this is how it has been done in the past > and because of performance reasons

Re: Fwd: [Patch] definitions in when, unless, do as well as in cond- and case-clauses

On Sun, Feb 06, 2022 at 10:45:54AM +0100, Linus Björnstam wrote: > You need to use ,optimize. Thanks you both, Maxime and Linus, for giving me a new lantern :) Cheers -- t signature.asc Description: PGP signature

Re: Fwd: [Patch] definitions in when, unless, do as well as in cond- and case-clauses

context which can be expensive. I > don't know guile internals but a let without any defines is trivially > converted to a begin by the optimizer. It seems that in Guile 3 the expander is smart enough for an empty bindings list in let: | tomas@trotzki:~$ guile | GNU Guile 3.0.7.6-2

Re: guile and libgccjit

On Sun, Oct 10, 2021 at 09:57:13AM +0200, Linus Björnstam wrote: > The the current JIT is, in my understanding, more or less a stepping stone > towards native compilation. The current JIT is very small and lightweight, > without any tracing, meaning things like register allocation is flexible >

Re: (inf) min max

On Tue, Sep 28, 2021 at 11:55:06AM +0200, Stefan Israelsson Tampe wrote: > Then this does not work well > > (fold min (inf) (list 1 > 200 > 3 4)) > > which is a pity, we

Re: more advanced bytevector => supervectors

On Thu, Sep 02, 2021 at 12:11:12PM -0700, Matt Wette wrote: > maybe guile could consider regexp's in scheme > see  https://ds26gte.github.io/pregexp/index.html This would have other advantages (e.g. suspendable match off a port), right? Cheers - t signature.asc Description: Digital signature

Re: Request to add *-resize! functions for contiguous mutable data structures.

On Sat, Aug 07, 2021 at 12:31:09PM +0200, Taylan Kammer wrote: > On 06.08.2021 16:33, Vijay Marupudi wrote: > > Hello! > > > > I was curious if Guile would be willing to provide a series of > > new procedures for resizing contiguous memory regions. [...] > Sounds like a good idea to me. I

Guile 3.0.7 can not be compiled on Fedora rawhide

Hi Guys, I am trying to package guile 3.0.7 into Fedora but I encountered a problem. In sources, there is a header lib/libc-config.h and then there is preprocessor condition for presence of __attribute_maybe_unused__ macro. This macro is newly defined in the latest version of glibc which we have

Re: Removal of hppa support

On Mon, Jan 27, 2020 at 12:30:15PM -0500, Stefan Monnier wrote: > > Initially in Guile I planned to use GNU Lightning, in part because of > > its great platform support. However it turned out to not be the right > > thing, and reluctantly I ended up doing something that was more like a > >

Re: GNU Guile 2.9.8 Released [beta]

but 2.9.8 found > > > Here's what I put in configure.ac: > GUILE_PKG(2.2 2.3 2.9 3.0) > > My question is "what's the correct config here"? Hm. I think I had that with nyacc too. This worked for me: GUILE_PKG([3.0]) GUILE_PROGS([2.9.5]) I think this is due to our currently

Re: GNU Guile 2.9.7 Released [beta]

(Sorry for the cross-post, see below) On Fri, Dec 13, 2019 at 09:23:46PM -0500, John Cowan wrote: > I am getting the following build error on both Cygwin and Ubuntu Xenial. > All is well until: > > BOOTSTRAP GUILEC system/vm/linker.go > /bin/bash: line 6: 16683 Segmentation fault (core

Re: 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)]

On Mon, Dec 02, 2019 at 05:09:42PM -0800, Matt Wette wrote: > > On 12/2/19 6:28 AM, Matt Wette wrote: > >I'm building 2.9.5 now but running into errors (ubuntu 18.04): > >/bin/bash: line 6: 14657 Segmentation fault  (core dumped) > >GUILE_AUTO_COMPILE=0 ../meta/build-env guild compile >

Re: 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)]

On Tue, Dec 03, 2019 at 10:15:35AM +0100, to...@tuxteam.de wrote: > On Mon, Dec 02, 2019 at 05:09:42PM -0800, Matt Wette wrote: > > > > On 12/2/19 6:28 AM, Matt Wette wrote: > > >I'm building 2.9.5 now but running into errors (ubuntu 18.04): > > [...] > > > So, as a random check, I first

Re: 2.9.5 build segfault on Ubuntu 18.04 [WAS: Nyacc and guile-nearly-3.0 (progress report)]

On Mon, Dec 02, 2019 at 05:09:42PM -0800, Matt Wette wrote: > > On 12/2/19 6:28 AM, Matt Wette wrote: > >I'm building 2.9.5 now but running into errors (ubuntu 18.04): [...] > So, as a random check, I first verified that I could reproduce the > above error at the command line.  I did. > > Then

Re: GNU Guile 2.9.5 Released [beta]

On Fri, Nov 22, 2019 at 04:22:39PM +0100, Andy Wingo wrote: > We are pleased to announce GNU Guile release 2.9.5. This is the fifth > pre-release of what will eventually become the 3.0 release series. Thanks! Compiling now. And oh, thank you for all the magic (and for explaining it to us mere

Re: Stepping back up as a co-maintainer

On Thu, Oct 17, 2019 at 12:24:03PM +0200, Mikael Djurfeldt wrote: > I think we should trust what Mark says and not second guess him. Definitely. I think this should count for *all*. Second-guessing anyone in this difficult situation can only add more difficulties on top. I think each of us

Re: missing word in "Building CPS" v 2.9.4

On Thu, Sep 05, 2019 at 07:04:07AM -0700, Matt Wette wrote: > The reference manual for 2.9.4, Section 9.4.4.3 titled "Building > CPS", paragraph 2, has sentence starting: > > "Construction is handled by a set of mutually builder macros:" > > I think there is a missing word between "mutually" and

Re: GNU Guile 2.9.4 Released [beta]

On Mon, Aug 26, 2019 at 03:12:47PM -0400, Mark H Weaver wrote: > Hi Thomas, > > Thomas Morley writes: [...] > > But I wonder, shouldn't it work out of the box with 'sudo make install' ? > > Running 'ldconfig' is not always appropriate, and therefore the vast > majority of programs do *not*

Re: GNU Guile 2.9.4 Released [beta]

On Mon, Aug 26, 2019 at 08:13:45PM +0200, Thomas Morley wrote: [...ldconfig...] > Hi tomás, > > thanks for your hints. > I've got it work by running nothing else than > sudo ldconfig > > But I wonder, shouldn't it work out of the box with 'sudo make install' ? As far as I know it should be

Re: GNU Guile 2.9.4 Released [beta]

On Mon, Aug 26, 2019 at 06:39:02PM +0200, Thomas Morley wrote: > Am So., 25. Aug. 2019 um 22:22 Uhr schrieb Andy Wingo : > > > > We are pleased to announce GNU Guile release 2.9.4. This is the fourth > > pre-release of what will eventually become the 3.0 release series. > > > We encourage you to

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

On Thu, Jun 06, 2019 at 05:40:39AM -0400, Mark H Weaver wrote: > 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

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

On Wed, May 15, 2019 at 07:25:37PM +0800, Nala Ginrut wrote: > hi Tomas! > For Guile, if you enabled suspendable-port, you may schedule the > blocking task captured by delimited continuation. > And use I/O multiplex mechanism (say, select or epoll) for monitoring > the file desc

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

On Wed, May 15, 2019 at 12:25:05PM +0100, Chris Vine wrote: > On Wed, 15 May 2019 12:09:19 +0200 > wrote: > > Sorry for this possibly dumb question [...] > With guile-2.2/3.0, you install suspendable ports and parameterize > current-read-waiter and/or current-write-waiter. There is an example

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

On Mon, May 13, 2019 at 06:54:38PM +0800, Nala Ginrut wrote: > Hi folks! > Here's a patch to add current-suspendable-io-status: > Its result is a pair: (finished-bytes . rest-bytes) Sorry for this possibly dumb question, but... is there a way to be non-blocking even if there are no

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

Just wow. I was aware for a while that Guile's I/O "story" wasn't stellar. So I was watching this thread, as my awe grew, mail by mail. Thanks Rob, Mark and all the others. This was really impressive. You rock. Cheers -- tomás signature.asc Description: Digital signature

Re: Compiling guile-2.2.4 for mingw

On Tue, Nov 20, 2018 at 03:31:25PM +0100, Christoph Buck wrote: > Hi! > > Currently i try to compile guile-2.2.4 under mingw64 bit. I had some > minor issues in the c source code which i managed to fix by applying > some of the patches from https://github.com/mkeeter/guile-mingw. Namely [...]

Re: multi-lingual guile: language strictness

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 13, 2018 at 07:53:51PM -0700, Matt Wette wrote: > Hi All, > > I posed a question on #guile IRC last weekend asking for use cases > for making Guile [...] > as another option, rename with an extension monicker (e.g., javascriptx)? +1 for

Re: A problem with licenses

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 30, 2018 at 01:36:43PM +0300, Tommi Höynälänmaa wrote: > > 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

Re: A problem with licenses

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, May 30, 2018 at 01:36:43PM +0300, Tommi Höynälänmaa wrote: > > 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

Re: Simple picture language

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 26, 2018 at 11:51:23PM +0200, Ricardo Wurmus wrote: > Hi Guilers, > > I wrote a simple SVG-based picture language. To try it: [...] > What do you think? Thanks for that! This prompted me to get my Geiser setup in working order and I

Re: Rename GNU fdisk to GUILE diskutils

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Dec 12, 2017 at 10:01:41PM -0200, David Pirotte wrote: > Hi Christian, > > > >> IMHO the programming language/compiler a utility is written with is an > > >> implementation detail that should not manifest itself in the utility's > > >>

Re: [PATCH] On Hurd, don't use not implemented madvise()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jun 02, 2017 at 10:00:18PM -0400, Mark H Weaver wrote: > writes: [...] > > This would at least suggest having a way to query whether madvise is > > available, through some introspection (giving the program a chance > > to

Re: [PATCH] On Hurd, don't use not implemented madvise()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 01, 2017 at 07:29:03PM -0400, Mark H Weaver wrote: > Manolis Ragkousis writes: [...] > > Also from my understanding not using madvise() ends up in slower > > performance but it doesn't create problems to the

Re: RFC: (ice-9 sandbox)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Apr 14, 2017 at 12:52:19PM +0200, Andy Wingo wrote: [...] > Concretely for this use case, assuming that we can solve the immutable > literal problem, I propose to remove sigils entirely. Thoughts welcome > here. There's still the "cultural

Re: Stuff I noticed compiling 2.0.13

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jan 06, 2017 at 08:14:11AM +0100, Michael Vehrs wrote: > Dear developers, > > on Debian 8.6 (jessie), configure failed to find the right > libreadline, or failed to determine its version. Despite having > libreadline 6.0 installed, configure

Re: GNU Guile 2.1.5 released (beta)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Dec 11, 2016 at 05:25:19PM -0800, Matt Wette wrote: [...] > Sorry to keep posting on this. I will stop soon. [this from the peanut gallery: feel free to ignore] Please don't! Even if I don't own a Mac, and even if I'll try to avoid that

Re: Slow compilation of guile-2.1.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Nov 28, 2016 at 09:47:08AM +0100, Jan Synáček wrote: > On Fri, Nov 25, 2016 at 9:36 AM, wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Fri, Nov 25, 2016 at 08:31:23AM +0100, Jan Synáček wrote: > >>

Re: Slow compilation of guile-2.1.x

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Nov 25, 2016 at 08:31:23AM +0100, Jan Synáček wrote: > Hello, > > while building guile-2.1.4 for Fedora, I noticed that the compilation > got *really* slow. I didn't measure it precisely, but as can be seen > from [1] (about 20 minutes) and

Re: srfi-1 take and drop seriously broken

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, Nov 20, 2016 at 05:32:25AM +0200, Eli Zaretskii wrote: > > Date: Sat, 19 Nov 2016 22:52:12 +0100 > > From: > > > > On Sat, Nov 19, 2016 at 10:18:21PM +0100, Jan Nieuwenhuizen wrote: > > > Jan Synáček writes: > > > > > > >

Re: srfi-1 take and drop seriously broken

(use-modules (srfi srfi-1)) > scheme@(guile-user)> (take '(list 1 2 3) 4) > $1 = (list 1 2 3) > scheme@(guile-user)> (drop '(list 1 2 3) 4) > $2 = () > --8<---cut here---end--->8--- Hm. Jan's example should work, nevertheless

Re: Web site now uses Haunt

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Nov 10, 2016 at 06:12:22PM +0100, Ludovic Courtès wrote: [...] > So now the news page is more pleasant to the eye: > > https://www.gnu.org/software/guile/news/ Nice! Like it. thanks - -- t -BEGIN PGP SIGNATURE- Version: GnuPG

Re: sxml simple, sxml->xml and namespaces

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 20, 2016 at 12:52:47PM +0200, Ricardo Wurmus wrote: [...] > Here is another proposal, mirroring what is done in “xml->sxml”: > Hey, thanks, Ricardo! Let me have a look at your patch and see whether I can wrap my head around it :-)

Re: sxml simple, sxml->xml and namespaces

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 20, 2016 at 10:56:26AM +0200, Andy Wingo wrote: > Greetings gentle Guiler, > > Apologies for the long delay here. No worries. Thanks for looking into it. I'm myself deeply embroiled in things (not Guile, alas!) so my response times

Re: Reading data from a file descriptor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 20, 2016 at 12:40:53PM +0200, Andy Wingo wrote: > On Tue 17 Nov 2015 14:55, Chris Vine writes: > > > On Tue, 17 Nov 2015 13:52:21 +0100 > >> On Tue, Nov 17, 2015 at 12:59:56PM +, Chris Vine wrote: [...]

Re: anyone define port types?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Mar 28, 2016 at 09:04:42PM +0200, Andy Wingo wrote: > Hi! > > I am working on improving our port implementation to take advantage of > the opportunity to break ABI in 2.2. I am wondering how much I can > break C API as well -- there are some

Re: [PATCH] gnu: Add erlang.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > On Mon 04 Jan 2016 06:20, Steve Sprang writes: > > > > > From http://www.erlang.org/download/otp_src_18.2.1.tar.gz... > > > ERROR: Bad qstring header component: kMSMAn68110840 [...] [Andy Wingo] > > The Etag value is

Re: Reading data from a file descriptor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Nov 23, 2015 at 10:07:11PM +0100, Andreas Rottmann wrote: > writes: [...] > > what Jan is after (and what I'd like to have too) is something > > akin to Unix read(2) with O_NONBLOCK: [...] > The procedure with the closest

Re: Reading data from a file descriptor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Nov 17, 2015 at 01:55:17PM +, Chris Vine wrote: > On Tue, 17 Nov 2015 13:52:21 +0100 > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On Tue, Nov 17, 2015 at 12:59:56PM +, Chris Vine wrote: > >

Re: Reading data from a file descriptor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Nov 16, 2015 at 11:54:33AM +0100, Amirouche Boubekki wrote: > On 2015-11-13 21:41, Jan Synáček wrote: [...] > >I have an open fd to a unix socket and I want to read data from it. I > >know that the data is going to be only strings, but I

Re: Reading data from a file descriptor

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Nov 13, 2015 at 10:51:58AM -0500, Mark H Weaver wrote: > Jan Synáček writes: > > > On Sun, Nov 8, 2015 at 12:49 AM, Andreas Rottmann > > wrote: > > > > Also note that if there's no requirement

Re: New logo and website design proposal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 12, 2015 at 03:26:21PM +0200, Ludovic Courtès wrote: > Aleix Conchillo Flaqué skribis: > > > I have a suggestion: would it be possible to show only one code sample in > > the Code examples section? [...] > I agree

Re: New logo and website design proposal

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Oct 12, 2015 at 01:15:59PM -0500, Luis Felipe López Acevedo wrote: [...] > I'm fine with Aleix suggestion. And it can be done so that the > examples are shown in a descent way without the effects for people > who don't use JavaScript.

Re: Guile Assembler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jun 23, 2015 at 02:28:41PM +0800, Nala Ginrut wrote: hi Panicz! On Mon, 2015-06-22 at 22:49 +0200, Panicz Maciej Godek wrote: My repo is available here: https://bitbucket.org/panicz/envy/src Thanks for the hint! There's tiny

Re: Guile Assembler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jun 23, 2015 at 05:19:56PM +0800, Nala Ginrut wrote: On Tue, 2015-06-23 at 11:12 +0200, to...@tuxteam.de wrote: What does number/base do? Does it change the read syntax of numbers? I think it defines a function (number/base base)

Re: Guile Assembler

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jun 23, 2015 at 05:30:42PM +0800, Nala Ginrut wrote: On Tue, 2015-06-23 at 11:27 +0200, to...@tuxteam.de wrote: Hm. Where's the difference to Guile's define? And why do you have double parentheses in your example? Still a bit lost.

sxml simple, sxml-xml and namespaces

against whatever version makes sense once we get some consensus on how to do it right. Thanks regards -- tomás --- /usr/share/guile/2.0/sxml/simple.scm 2012-03-18 20:16:21.0 +0100 +++ /home/tomas/lib/guile/sxml/simple.scm 2015-04-08 22:29:30.049277842 +0200 @@ -37,29 +37,38 @@ argument

Re: [PATCH] Per-module reader, take #3

On Fri, Dec 16, 2005 at 08:32:02AM +, Neil Jerram wrote: [EMAIL PROTECTED] (Tomas Zerolo) writes: On Thu, Dec 15, 2005 at 07:47:13PM +, Neil Jerram wrote: [EMAIL PROTECTED] (Ludovic Courtès) writes: OTOH, http://community.schemewiki.org/?variable-naming-convention suggests

Re: [PATCH] Per-module reader, take #3

someone coming to Scheme from another language for the first time? To be fair, they seem just to be reporting on current use (which is an useful service). Now I'm not implying to say that I like current use (which is somewhat fragmented across Scheme implementations as well). Regards -- tomas

Re: [PATCH] Per-module reader, take #2

On Thu, Oct 20, 2005 at 09:48:50AM +0200, Ludovic Court?s wrote: Hi Neil, Neil Jerram [EMAIL PROTECTED] writes: I don't think it should be connected with modules, though. In my view: - modules should be about identifier access and visibility (including issues such as possible