Re: include can't work

On Sun, 2013-11-17 at 05:09 -0500, Mark H Weaver wrote: > Guile's 'include' also supports relative paths if the (include "...") > form is found within a file, or more generally, if it was read from a > port that had its filename set. > > Please tell us more about what you were doing, so that we ca

Re: Improving R6RS exception handling in Guile

Sorry for the long delay on this. Göran Weinholt writes: > Mark H Weaver writes: > >> Hello all, >> >> I've cooked up a patch to help improve R6RS exception handling in Guile. >> >> As noted by Göran Weinholt in , the R6RS >> exception handlers in Guile are currently

Re: include can't work

l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> Here's a patch to improve the error message. >> I'll push it to stable-2.0 if there are no objections. > > Looks good to me, but s/pathname/file name/? Okay, I made that change and pushed it to stable-2.0. Thanks, Ma

[PATCH] Make guardians and (ice-9 popen) thread-safe

Hello all, Here's a set of patches for stable-2.0 that make (ice-9 popen) and guardians thread-safe. These patches fix . (please disregard the preliminary patches I posted in that bug report). These patches also lay the groundwork for conveniently blocking asyncs while

Re: [PATCH] Add procedures to convert alists into hash tables

Hi David, David Thompson writes: > +@deffn {Scheme Procedure} alist->hash-table alist > +@deffnx {Scheme Procedure} alist->hashq-table alist > +@deffnx {Scheme Procedure} alist->hashv-table alist > +@deffnx {Scheme Procedure} alist->hashx-table hash assoc alist > +Convert @var{alist} into a hash

Re: [PATCH] Add procedures to convert alists into hash tables

On 11/17/2013 08:50 PM, David Thompson wrote: > Finally got around to updating this patch. I opted for adding a > standalone module named (ice-9 hash-table) rather than including it from > boot-9. > > How did I do? > > - Dave > Forgot to add the new module file to Makefile.am. Updated patch at

Re: [PATCH] Add procedures to convert alists into hash tables

On 11/06/2013 07:54 AM, Ludovic Courtès wrote: > Mark H Weaver skribis: > >> "Thompson, David" writes: >> >>> On Tue, Oct 29, 2013 at 8:38 AM, Ludovic Courtès wrote: I think it would make sense to implement them in Scheme, say in ice-9/hash-table.scm, which could be either a separate

Re: There is no returning

Ludovic Courtès wrote: > What would you think of sticking to the standard and less problematic > ‘_Noreturn’ identifier in Gnulib? That's what Gnulib does already. Other than the stdnoreturn module itself, Gnulib modules always use _Noreturn rather than noreturn. This is not merely because of n

Re: There is no returning

Bruce Korb skribis: > On 11/17/13 13:18, Ludovic Courtès wrote: >> What would you think of sticking to the standard and less problematic >> ‘_Noreturn’ identifier in Gnulib? >> >> (I also agree that it’s better for Guile’s public headers to use >> ‘__noreturn__’, but using ‘noreturn’ was not comp

Re: There is no returning

On 11/17/13 13:18, Ludovic Courtès wrote: What would you think of sticking to the standard and less problematic ‘_Noreturn’ identifier in Gnulib? (I also agree that it’s better for Guile’s public headers to use ‘__noreturn__’, but using ‘noreturn’ was not completely silly either.) "noreturn" i

Re: There is no returning

Paul Eggert skribis: > A better solution, if you want to be portable to > MSVC, is to use _Noreturn instead of noreturn. > This is for reasons described in stdnoreturn.in.h. > > '_Noreturn' is a bit ugly; if you don't care about > MSVC, then __attribute__((__noreturn__)) is > a good way to go. N

Re: include can't work

Mark H Weaver skribis: > Mark H Weaver writes: >> Obviously the error message should be improved, but the upshot is this: >> if you want to use 'include' from the REPL, or from some other port with >> no associated filename, then you must pass it an absolute pathname. > > Here's a patch to impro

Re: include can't work

Nala Ginrut writes: > 2013-11-17 AM11:19 "Mark H Weaver" ： >> When you're at the REPL, why not just use 'load' instead? > > Thanks for the explain, but it's not used in a REPL. I just used the > REPL to explain the issue. In that case, can you tell us where the 'include' macro was used? > Rack

Re: include can't work

2013-11-17 AM11:19 "Mark H Weaver" ： > When you're at the REPL, why not just use 'load' instead? Thanks for the explain, but it's not used in a REPL. I just used the REPL to explain the issue. Racket's "include" support relative path, so I made the mistake. > > Thoughts? > >Mark