unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: Fwd: Guile's SCM_DEFINE and Semantic mode
Date: Mon, 03 Nov 2014 00:12:50 +0100	[thread overview]
Message-ID: <87wq7dgpsd.fsf@gnu.org> (raw)
In-Reply-To: 5456B125.3050509@gnu.org

Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> skribis:

> I'm working on a libguile-based project.  All function definitions that
> are exported from C code to the Guile interpreter are define like this:
> (meta-variables between '<' and '>')
>
> SCM_DEFINE (<c-name>, <scheme-name>,
>             <mandatory-args-count>, <optional-args-count>, <rest-bool>,
>             <argument-list>,
> 	    <documentation-string>)
> {
>  <function-body>
> }
>
> At C preprocessing time the 'SCM_DEFINE (...)' function header gets
> expanded to:
>
> SCM
> <c-name> <c-argument-list>
>
> Unfortunately Semantic doesn't recognize it as a function definition.
> How can I make Semantic recognize it as such?

I don’t know about Semantic, but I know that GNU GLOBAL doesn’t have any
problems dealing with SCM_DEFINE’d functions.

So perhaps the simplest way is to use xgtags.el or similar, or to tell
Semantic to use GLOBAL as its back-end (info "(semantic) SymRef")?

Ludo’.




  reply	other threads:[~2014-11-02 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5454F895.9050005@gnu.org>
2014-11-02 22:33 ` Fwd: Guile's SCM_DEFINE and Semantic mode Bruno Félix Rezende Ribeiro
2014-11-02 23:12   ` Ludovic Courtès [this message]
2014-11-03 22:52     ` Bruno Félix Rezende Ribeiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq7dgpsd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).