snarf .h files

snarf .h files

[Mike Gran]

Hi-
 
Is there a script that will scrape SCM_DEFINEs from c files
to make header declarations to put in .h files?
 
Basically to search for c file definitions like this...
 
SCM_DEFINE (cfunc, "gfunc", 1, 0, 0, (SCM arg), "a function");
 
and return header declarations like this
 
SCM cfunc (SCM arg);
 
(It is an easy problem, but, I figured I'd be lazy and
ask.)
 
Thanks,
 
Mike Gran

Re: snarf .h files

[Ludovic Courtès]

Hi Mike,

Mike Gran <spk121@yahoo.com> skribis:

> Basically to search for c file definitions like this...
>  
> SCM_DEFINE (cfunc, "gfunc", 1, 0, 0, (SCM arg), "a function");
>  
> and return header declarations like this
>  
> SCM cfunc (SCM arg);

There’s no such tool AFAIK, but you can always come up with one.  :-)

The tools at
<http://git.savannah.gnu.org/cgit/gnutls.git/tree/guile/modules/system/documentation>
could serve as a starting point, I think.

Thanks,
Ludo’.

Re: snarf .h files

[Mike Gran]

> From: Ludovic Courtès <ludo@gnu.org>

>> Basically to search for c file definitions like this...
>>  
>> SCM_DEFINE (cfunc, "gfunc", 1, 0, 0, (SCM arg), "a function");
>>  
>> and return header declarations like this
>>  
>> SCM cfunc (SCM arg);
>
>There’s no such tool AFAIK, but you can always come up with one.  :-)


Cool.  I was able to cobble something together.


>The tools at
><http://git.savannah.gnu.org/cgit/gnutls.git/tree/guile/modules/system/documentation>
>could serve as a starting point, I think.

There's a argument ordering bug in your output.scm. The procedure

run-cpp-and-extract-snarfing expects (1) file, (2) cpp, (3) cpp-flags
but it is passed (2) cpp, (1) c-file, (3) cflags from within

output-procedure-texi-documentation-from-c-file.

Thanks,

Mike

Re: snarf .h files

[Ludovic Courtès]

Hey,

Mike Gran <spk121@yahoo.com> skribis:

>> From: Ludovic Courtès <ludo@gnu.org>
>
>>> Basically to search for c file definitions like this...
>>>  
>>> SCM_DEFINE (cfunc, "gfunc", 1, 0, 0, (SCM arg), "a function");
>>>  
>>> and return header declarations like this
>>>  
>>> SCM cfunc (SCM arg);
>>
>>There’s no such tool AFAIK, but you can always come up with one.  :-)
>
>
> Cool.  I was able to cobble something together.
>
>
>>The tools at
>><http://git.savannah.gnu.org/cgit/gnutls.git/tree/guile/modules/system/documentation>
>>could serve as a starting point, I think.
>
> There's a argument ordering bug in your output.scm. The procedure
>
> run-cpp-and-extract-snarfing expects (1) file, (2) cpp, (3) cpp-flags
> but it is passed (2) cpp, (1) c-file, (3) cflags from within
>
> output-procedure-texi-documentation-from-c-file.

Oh nice.  :-)  This one is actually unused, though.

Thanks!

Ludo’.