dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Emil Velikov <emil.l.velikov@gmail.com>
To: "Tapani Pälli" <tapani.palli@intel.com>, dri-devel@lists.freedesktop.org
Cc: emil.l.velikov@gmail.com
Subject: Re: [PATCH] intel: wrap intel_bufmgr.h C code for C++ compilation/linking
Date: Fri, 3 Jul 2015 16:44:05 +0100	[thread overview]
Message-ID: <5596ADC5.3020607@gmail.com> (raw)
In-Reply-To: <1435750639-6090-1-git-send-email-tapani.palli@intel.com>

On 01/07/15 12:37, Tapani Pälli wrote:
> (We need this include in porting changes for the OpenGL ES
> conformance suite.)
> 
> Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
> ---
>  intel/intel_bufmgr.h | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/intel/intel_bufmgr.h b/intel/intel_bufmgr.h
> index 285919e..f061454 100644
> --- a/intel/intel_bufmgr.h
> +++ b/intel/intel_bufmgr.h
> @@ -38,6 +38,10 @@
>  #include <stdint.h>
>  #include <stdio.h>
>  
> +#if defined(__cplusplus) || defined(c_plusplus)
> +extern "C" {
> +#endif
> +
Strongly in favour - I've been pondering on this for a very long time.
Just a question - is there a compiler that care about (something from
the last decade) that does not define __cplusplus but c_plusplus ?

Afaict the former is defined since (at least) the 1998 C++ standard,
while the latter is extremely rare, and mostly mentioned as decrecated.

-Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-07-03 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01 11:37 [PATCH] intel: wrap intel_bufmgr.h C code for C++ compilation/linking Tapani Pälli
2015-07-03 15:44 ` Emil Velikov [this message]
2015-07-27  9:59   ` Tapani Pälli
2015-07-28 15:25     ` Emil Velikov

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=5596ADC5.3020607@gmail.com \
    --to=emil.l.velikov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tapani.palli@intel.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