Hi Andy,
> It should work now, though with hacks -- if you manipulate the
> module-public-interface directly. But perhaps some more baked in support
> would be useful.
Oh, certainly -- as I've learned over these many months, you can do
some very interesting things by working with the lower-level
Hi Julian,
On Sun 25 Oct 2009 18:16, Julian Graham writes:
> --- a/libguile/gc-malloc.c
> +++ b/libguile/gc-malloc.c
> @@ -206,7 +206,8 @@ void *
> scm_gc_calloc (size_t size, const char *what)
> {
>void *ptr = scm_gc_malloc (size, what);
> - memset (ptr, 0x0, size);
> + if (size)
> +
Hi Julian,
On Sat 24 Oct 2009 21:10, Julian Graham writes:
> Besides version, another thing that would be very useful to have
> "native" Guile support for is being able to export bindings with names
> other than the ones given to them within the module
It should work now, though with hacks -- i
Applied, thanks!
Ludo'.
Hey!
Andy Wingo writes:
> The '(args) is duplicated, the compiler notices that, and stores it only
> once. When the memoizer processes the '(args) *argument* it memoizes
> args to point to its lexical location (#...@0+0; I didn't show the let in
> my example). But that side-effects the formals o
Hi,
Neil Jerram writes:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> Neil Jerram writes:
>>
>>> I noticed that the docs on the Guile web pages are a bit out of date.
>>> The 1.8 ones are behind those in 1.8.7 (the latest release).
>>
>> http://www.gnu.org/software/guile/manual/html_node/index.
Hi all,
I've been fixing and reverting this locally for the past month or so,
and I'm not sure if anyone else has seen this, but it looks like
there's some static analysis code that's been added to GCC 4.3.3 that
warns about code paths that could produce a call to `memset' with a
size parameter of
