From: "Tapani Pälli" <tapani.palli@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] intel: wrap intel_bufmgr.h C code for C++ compilation/linking
Date: Mon, 27 Jul 2015 12:59:22 +0300 [thread overview]
Message-ID: <55B600FA.9000109@intel.com> (raw)
In-Reply-To: <5596ADC5.3020607@gmail.com>
On 07/03/2015 06:44 PM, Emil Velikov wrote:
> 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 ?
I don't know, this was just copy paste from other file.
> Afaict the former is defined since (at least) the 1998 C++ standard,
> while the latter is extremely rare, and mostly mentioned as decrecated.
For me it is ok to drop c_plusplus, no strong opinion.
> -Emil
>
// Tapani
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-07-27 9:59 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
2015-07-27 9:59 ` Tapani Pälli [this message]
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=55B600FA.9000109@intel.com \
--to=tapani.palli@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.