On Tue, 15 Oct 2013 10:05:41 -0300 Felipe Magno de Almeida
said:
> On Tue, Oct 15, 2013 at 4:31 AM, Michael Blumenkrantz
> wrote:
> > rejected, this patch completely breaks build.
>
> Sorry, forgot to add more files to the patch. I've also changed for
> the EAPI to have extern "C"
> when compil
On Thu, Oct 10, 2013 at 10:02 PM, Lucas De Marchi <
lucas.demar...@profusion.mobi> wrote:
> I find intriguing why would anyone create an enlightenment module in
> c++. What are the advantages?
>
The elev8 extension is written in C++ because it uses V8, for instance.
--
Leandro
---
On Tue, Oct 15, 2013 at 4:31 AM, Michael Blumenkrantz
wrote:
> rejected, this patch completely breaks build.
Sorry, forgot to add more files to the patch. I've also changed for
the EAPI to have extern "C"
when compiling with a C++ compiler instead of making blocks of extern
"C" for all headers.
rejected, this patch completely breaks build.
On Mon, Oct 14, 2013 at 11:52 PM, Felipe Magno de Almeida <
felipe.m.alme...@gmail.com> wrote:
> Hello,
>
> This patch allows C++ code to #include installed headers for
> enlightenment to create modules in C++.
>
> Any comments are appreciated.
>
> R
Hello,
This patch allows C++ code to #include installed headers for
enlightenment to create modules in C++.
Any comments are appreciated.
Regards,
--
Felipe Magno de Almeida
c++.patch
Description: Binary data
--
Octob
On Fri, Oct 11, 2013 at 3:06 AM, Carsten Haitzler wrote:
> On Fri, 11 Oct 2013 00:03:00 + Felipe Magno de Almeida
> said:
>
>> Hello,
>>
>> Currently, writing modules for enlightenment using C++ is not possible
>> without modifying headers from enlightenment.
>>
>> How is the policy for these
On Fri, 11 Oct 2013 03:18:37 +0200
Cedric BAIL wrote:
> Hello,
>
> On Fri, Oct 11, 2013 at 2:03 AM, Felipe Magno de Almeida
> wrote:
> > Currently, writing modules for enlightenment using C++ is not possible
> > without modifying headers from enlightenment.
> >
> > How is the policy for these h
On Fri, 11 Oct 2013 00:03:00 + Felipe Magno de Almeida
said:
> Hello,
>
> Currently, writing modules for enlightenment using C++ is not possible
> without modifying headers from enlightenment.
>
> How is the policy for these headers w.r.t C++ compatibility?
>
> The most common problems are
Hello,
On Fri, Oct 11, 2013 at 2:03 AM, Felipe Magno de Almeida
wrote:
> Currently, writing modules for enlightenment using C++ is not possible
> without modifying headers from enlightenment.
>
> How is the policy for these headers w.r.t C++ compatibility?
>
> The most common problems are:
> * La
On Thu, Oct 10, 2013 at 9:03 PM, Felipe Magno de Almeida
wrote:
> Hello,
>
> Currently, writing modules for enlightenment using C++ is not possible
> without modifying headers from enlightenment.
>
> How is the policy for these headers w.r.t C++ compatibility?
>
> The most common problems are:
> *
Hello,
Currently, writing modules for enlightenment using C++ is not possible
without modifying headers from enlightenment.
How is the policy for these headers w.r.t C++ compatibility?
The most common problems are:
* Lack of extern "C";
* The use of C++ keywords, e.g., class (replaced for klass)
11 matches
Mail list logo