Weirdness in guile manual

Hello, I just noticed something fishy in the web version of the guile manual. I was trying to read something about breakpoints and I came across this page: http://www.gnu.org/software/guile/manual/html_node/Intro-to-Breakpoints.html#Intro-to-Breakpoints The heading says "3.4.2 Intro to Breakpoin

Re: Weirdness in guile manual

That looks like my old 'GDS' stuff, from before the 2.0 change; I don’t believe any of it is applicable any more, so that node should just be deleted.        Neil    Original Message   From: Jan Synáček Sent: Sunday, 29 November 2015 13:10 To: guile-devel Subject: Weirdness in guile manual Hel

Re: Weirdness in guile manual

n...@ossau.homelinux.net skribis: > That looks like my old 'GDS' stuff, from before the 2.0 change; I don’t > believe any of it is applicable any more, so that node should just be > deleted.  Indeed, I’ve removed it now. Ludo’.

Re: Announcing 8sync: an asynchronous programming language for Guile

Christopher Allan Webber skribis: > Christopher Allan Webber writes: > >> ... and the complicated-number-code will launch asynchronously, but wake >> back up the appropriate function appropriately. You can also set timed >> events, read and write to ports asynchronously, and etc. It has a nice

Re: guile's web - a few things

David Pirotte skribis: > Cool work, super nice site, .. thanks all! > A couple of things...: Could you send these suggestions as patches? We’ll happily apply them! The repository is at , with applications defined at

Re: Announcing 8sync: an asynchronous programming language for Guile

Christopher Allan Webber skribis: > It makes significant use of delimited continuations. You can do things > like this: > > (define (my-number-talker) > (format #t > "Oh boy, looks like we got back ~a!\n" > (%sync (%run (+ 1 2 3 (complicated-number-code 38)) > > ... and the

Re: Announcing 8sync: an asynchronous programming language for Guile

Ludovic Courtès writes: > Christopher Allan Webber skribis: > >> Christopher Allan Webber writes: >> >>> ... and the complicated-number-code will launch asynchronously, but wake >>> back up the appropriate function appropriately. You can also set timed >>> events, read and write to ports asynchr