From: "Dale P. Smith" <dsmith@altustech.com>
Subject: Re: More on module API
Date: Fri, 16 Aug 2002 16:56:30 -0400 [thread overview]
Message-ID: <20020816165630.54f945e7.dsmith@altustech.com> (raw)
In-Reply-To: <20020812192938.GA2749@www>
On Mon, 12 Aug 2002 21:29:38 +0200
rm@fabula.de wrote:
>
> - looking at the code emited by the current snarfer i realized that
> the function isn't declared 'static' (NOTE: my version of SCM_DEFINE_PUBLIC
> declares the function to be static). Is this intentional? I can't think of a
> reason to export the function on the C level.
>
Lots of Guile C code calls the C functions directly. If declared
static, they could only be called from within the same source file.
-Dale
--
Dale P. Smith
Senior Systems Consultant, | Treasurer,
Altus Technologies Corporation | Cleveland Linux Users Group
dsmith@altustech.com | http://cleveland.lug.net
440-746-9000 x339 |
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-16 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 19:29 More on module API rm
2002-08-16 20:56 ` Dale P. Smith [this message]
2002-08-31 13:49 ` Marius Vollmer
2002-08-31 18:32 ` Dale P. Smith
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=20020816165630.54f945e7.dsmith@altustech.com \
--to=dsmith@altustech.com \
/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).