edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] extern "C"{}
Date: Sat, 15 Feb 2014 03:52:37 -0500	[thread overview]
Message-ID: <20140115035237.eklhad@comcast.net> (raw)

I've seen it manyh times, but I don't understand what this does.
I would guess that the prototypes enclosed are C functions,
not C++, so the C++ compiler will call them with the C conventions.
That would make sense, but then

1. Couldn't we just put it around eb.p?
We don't really need it in eb.h.
That would let us indent eb.h if we like, and be a bit clearer perhaps.

2. there are a few functions like set_global_property_string
that are C++ functions, but are declared in eb.p, in eb.h,
and inside extern "C"{}.
In fact this one is declared twice, in eb.p and ebjs.p, one inside extern "C"{}
and the other time not.

So I guess I don't know what this does,
and why we seem to get away with using it inconsistently.

Karl Dahlke

             reply	other threads:[~2014-02-15  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15  8:52 Karl Dahlke [this message]
2014-02-16 20:40 ` Adam Thompson
2014-02-16 23:40 Karl Dahlke
2014-02-17 16:43 ` Adam Thompson

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

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

  git send-email \
    --in-reply-to=20140115035237.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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 NNTP newsgroup(s).