Kevin Ryde <[EMAIL PROTECTED]> writes:
> I made some memory leak checks for myself by demanding that
> "(assoc-ref (gc-stats) 'bytes-malloced)" was steady across some
> repetitions of a test. That's actually a different number though (is
> it?), but it should in theory be possible to exercise som
I may be chasing pure randomness, but I find that the only file that cannot
be compiled -O2 is read.c -- I can switch back and forth between the segfault
and the stack overflow just by changing the optimization switch on that
file (optimizing all the rest).
Hi,
I think it'd be nice to export `scm_i_mem2number ()'. My initial plan
was to just rename it `scm_c_string_to_number ()' and document it.
However, due to the eventual support for various encodings, we'd rather
need to have something like `scm_c_locale_string_to_number ()'. The
problem is: ho
[EMAIL PROTECTED] (Ludovic Courtès) writes:
> I think it'd be nice to export `scm_i_mem2number ()'. My initial plan
> was to just rename it `scm_c_string_to_number ()' and document it.
>
> However, due to the eventual support for various encodings, we'd rather
> need to have something like `scm_c
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> That is, in both branches? :-)
No, in 1.8. Someone can do merges into the head (there isn't anything
in 1.8 which isn't also meant to be in the head, yet).
___
Guile-devel mailing list
Guile-devel@gnu.o
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> However, due to the eventual support for various encodings, we'd rather
> need to have something like `scm_c_locale_string_to_number ()'.
That could be more relaxed than specifically the "locale" encoding.
If all valid numbers are ascii then it doesn
[EMAIL PROTECTED] (Ludovic Courtès) writes:
>
> a periodic distribution whose period is unknown
The idea is to force gc's before and after, expecting mem counters to
be unchanged by the test code in the middle. I had to setup for
multiple attempts, I guess memoizing or other freaky stuff happens
