Neil Jerram <[EMAIL PROTECTED]> writes:
> guile-debugging should be able to accumulate coverage of all source
> expressions - say in a particular file - but it might incur a big
> performance cost in so doing. I'll try this out and let you know what
> I find.
For the record, here is how one can
Kevin Ryde <[EMAIL PROTECTED]> writes:
> I wrote a few words for scm_set_program_arguments, which is mentioned
> under scm_boot_guile but not otherwise described.
Looks good, just one comment:
> scm_set_program_arguments (-1, argv+i, progname);
Is argv normally NULL-terminated? I w
Kevin Ryde <[EMAIL PROTECTED]> writes:
> How about making scm_set_program_arguments() available at the scheme
> level too? As say
>
> (set-program-arguments lst)
>
> (without the "first" arg business of the C level).
>
> The C func is good for when you munch some options at the C level in
>
I wrote a few words for scm_set_program_arguments, which is mentioned
under scm_boot_guile but not otherwise described.
-- C Function: void scm_set_program_arguments (int argc, char **argv,
char *first)
Set the list of command line arguments to be returned by
`program-argume
How about making scm_set_program_arguments() available at the scheme
level too? As say
(set-program-arguments lst)
(without the "first" arg business of the C level).
The C func is good for when you munch some options at the C level in
an scm_boot_guile, having it at the scheme level wou
In regexp-exec in 1.8, a nul in the input string, or a bad flags arg,
results in a throw from a critical section, which calls abort(). Eg.
(regexp-exec (make-regexp "x") "\0")
=> abort
(regexp-exec (make-regexp "x") "hello" 0 'badflags)
=> abort
What's the reason
