Re: no more *.la files in libgc-dev

David Pirotte writes: > Le Sun, 26 Jun 2011 22:15:23 +0200, > Andreas Rottmann a écrit : > > ... >> The solution (other than just removing the offending .la files) would be to >> re-build and re-install all software depending on libgc-dev, including >> g-wrap, as to get rid of the stale referenc

Re: pending branch: lexical-literals

Hi, On Fri 29 Apr 2011 17:16, Andy Wingo writes: > I have a branch that fixes literal matching to actually compare toplevel > bindings, as the RNRS suggest, rather than simply assuming that a > literal that is not lexically bound can be compared symbolically. In the end I think this is too disr

when and unless

I think we should add `when' and `unless' to the default environment. They go like this: (define-syntax when (syntax-rules () ((_ test then then* ...) (if test (begin then then* ... (if #f #f)) (define-syntax unless (syntax-rules () ((_ test else else* ...)

Re: enhancement requests ("load-ignoring-cached-go")

Hi! On Thu 21 Apr 2011 17:56, Wolfgang J Moeller writes: > btw., in R6RS and this latest "pre-R6RS" 'psyntax', the first argument > to datum->syntax must be an identifier, not an arbitrary syntax > form. Permitting the latter in the old 'psyntax' might have been a > mistake ... I've still got t

Re: How can I tell guile to shut up? ;)

Hi Andreas, Thanks for looking at the patch! On Thu 30 Jun 2011 03:24, Andreas Rottmann writes: > Andy Wingo writes: > >> After some thinking, the base thing to do is just to add a warning port, >> and make warnings (non-fatal informative messages) write to that port. >> I have done this in th

Re: Building without posix

On Sat 02 Apr 2011 17:25, Dmitry Dzhus writes: > Also similar error when building without dynamic modules support: > > CCLD libguile-2.0.la > CCLD guile > ./.libs/libguile-2.0.so: undefined reference to `scm_dynamic_link' > ./.libs/libguile-2.0.so: undefined reference to `scm_dynamic_call

Re: %load-hook only used within primitive-load?

Hi nalaginrut, On Thu 14 Apr 2011 12:05, nalaginrut writes: > I found the manual said "%load-hook is used by all of the above loading > functions (load,load-path, primitive-load and primitive-load-path)". > But it seems only "primitive-load" according to it. Fixed, thanks for the report. Andy

Re: Patch: New section "Invoking Guile" for chapter "Programming in Scheme"

Hi Mark, On Mon 25 Apr 2011 21:49, Mark Harig writes: >> >> > On Sun, Apr 24, 2011 at 04:33:44PM +0200, Andy Wingo wrote: >> >> your patches should be "atomic" >> > >> > "3. No patch introduces a regression: after applying any >> > initial part of the series, the resulting project still >> > co

Re: Building without posix

Hi! A bit late, but... On Fri 15 Apr 2011 00:17, l...@gnu.org (Ludovic Courtès) writes: > Dmitry Dzhus writes: > >> Is POSIX module considered optional? > > Not really. > >> Configuring guile-2.0 and git trunk with --disable-posix results in the >> following error on my x86: > > I pushed a patc

Re: [PATCH 2/5] [mingw]: Have compiled-file-name produce valid names.

On Fri 20 May 2011 15:47, Jan Nieuwenhuizen writes: > Andy Wingo writes: > >> I don't much like this approach. Besides mixing in a heuristic on all >> machines that is win32-specific, it makes c:/foo.scm collide with >> d:/foo.scm in the cache, and fails to also modify load.c which also does >>

Re: Building without posix

Hello! Andy Wingo skribis: > I think we should focus on the GNU system, using gnulib to adapt other > systems to look like GNU. Disabling POSIX bindings helps no one on the > GNU system -- if the question is one of library size, the solution > should be loadable modules, not compile-time option

Re: Building without posix

Hi :) On Thu 30 Jun 2011 16:17, l...@gnu.org (Ludovic Courtès) writes: > I think the compile-time option can be useful when building on a “raw” > or old system, which doesn’t support all the POSIX bits we wrap, or on a > slow system. But we check for all of the bits we do wrap, no? It seems to

Re: How can I tell guile to shut up? ;)

Hi Andy, Andy Wingo skribis: > After some thinking, the base thing to do is just to add a warning port, > and make warnings (non-fatal informative messages) write to that port. > I have done this in the attached patches. Any objections? Ideally I’d preferred to keep current-warning-port in (sy

Re: How can I tell guile to shut up? ;)

Hi! Andy Wingo skribis: > 4) Our fluids currently have problems with threads: if a thread not > spawned by a Guile thread enters Guile, its fluids are bound to > #f. This should be fixed; in the meantime though we hack around > that with the (or ...) clause, which is not a hack

Re: when and unless

Hello comrade! Andy Wingo skribis: > I think we should add `when' and `unless' to the default environment. [...] > These are pretty uncontroversial What?! http://lists.r6rs.org/pipermail/r6rs-discuss/2007-March/thread.html#1856 Here’s another argument: these macros are about writing imper