On Thursday 14 August 2014 10:04:55 Gour wrote:
> On Wed, 13 Aug 2014 17:20:51 -0700
>
> John Ralls wrote:
> > Then I can make a C++ class and move the functionality into
> > it one function at a time, converting the C function to a wrapper
> > with C linkage. I can test that against the existing
On Wed, 13 Aug 2014 17:20:51 -0700
John Ralls wrote:
> Then I can make a C++ class and move the functionality into
> it one function at a time, converting the C function to a wrapper
> with C linkage. I can test that against the existing C tests, add C++
> tests, and move on to the next function.
Its very possible to begin he transition to C++ by writing C++ header files.
The real advantage of C++ is the ability to take a specification (in my
case the Intel IBIS electronic buffer modeling specification
http://www.eigroup.org/ibis/ibis.htm) and modelling it with C++ header
files that compi
On Aug 13, 2014, at 3:42 PM, Gour wrote:
> On Wed, 13 Aug 2014 11:21:59 -0400
> Derek Atkins wrote:
>
>> Ummm.. No.
>
> OK.
>
>> The benefit of C -> C++ is that except for a few minor issues with
>> keywords you can *generally* compile C code using the C++ compiler and
>> it will *just work*
On Wed, 13 Aug 2014 11:21:59 -0400
Derek Atkins wrote:
> Ummm.. No.
OK.
> The benefit of C -> C++ is that except for a few minor issues with
> keywords you can *generally* compile C code using the C++ compiler and
> it will *just work*.
That's clear.
> The same cannot be said for Go or any
Gour writes:
> On Tue, 5 Aug 2014 11:04:00 -0700
> John Ralls wrote:
>
> Hello all,
>
>> What is the motivation for compiling everything as C++ if it's still
>> really C and you have to wrap everything in extern "C" {} to get it
>> to link, especially in gnome and register directories, which can
On Tue, 5 Aug 2014 11:04:00 -0700
John Ralls wrote:
Hello all,
> What is the motivation for compiling everything as C++ if it's still
> really C and you have to wrap everything in extern "C" {} to get it
> to link, especially in gnome and register directories, which can't be
> converted to C++?
On Aug 12, 2014, at 7:22 AM, Aaron Laws wrote:
> On Mon, Aug 11, 2014 at 4:52 PM, Christian Stimming
> wrote:
>
>> Hi Aaron,
>>
>> thanks for investing time in Gnucash and also in its development towards
>> more
>> future-proof programming technologies.
>
>
> The pleasure is mine.
>
>
>>
On Mon, Aug 11, 2014 at 4:52 PM, Christian Stimming
wrote:
> Hi Aaron,
>
> thanks for investing time in Gnucash and also in its development towards
> more
> future-proof programming technologies.
The pleasure is mine.
> I was a bit puzzled about the benefit
> of switching the "normal compilin
On Aug 11, 2014, at 4:52 PM, Christian Stimming wrote:
> thanks for investing time in Gnucash and also in its development towards more
> future-proof programming technologies. I was a bit puzzled about the benefit
> of switching the "normal compiling" from C to C++, just by itself. IMHO,
> th
Hi Aaron,
thanks for investing time in Gnucash and also in its development towards more
future-proof programming technologies. I was a bit puzzled about the benefit
of switching the "normal compiling" from C to C++, just by itself. IMHO, there
is of course an immediate benefit if the data struc
On Wednesday 06 August 2014 19:15:35 John Ralls wrote:
> On Aug 6, 2014, at 2:16 PM, Geert Janssens wrote:
> > On Wednesday 06 August 2014 16:16:17 Aaron Laws wrote:
> >> I tried to follow the directions at
> >> http://wiki.gnucash.org/wiki/Contributing_to_GnuCash, but I
> >> couldn't
> >> find a
On Aug 6, 2014, at 2:16 PM, Geert Janssens wrote:
> On Wednesday 06 August 2014 16:16:17 Aaron Laws wrote:
>> I tried to follow the directions at
>> http://wiki.gnucash.org/wiki/Contributing_to_GnuCash, but I couldn't
>> find a Bugzilla issue encapsulating the Great C++ Refactor. Should I
>> cre
On Wednesday 06 August 2014 16:16:17 Aaron Laws wrote:
> I tried to follow the directions at
> http://wiki.gnucash.org/wiki/Contributing_to_GnuCash, but I couldn't
> find a Bugzilla issue encapsulating the Great C++ Refactor. Should I
> create one so there is a place to put patches?
>
> I learned
I tried to follow the directions at
http://wiki.gnucash.org/wiki/Contributing_to_GnuCash, but I couldn't find a
Bugzilla issue encapsulating the Great C++ Refactor. Should I create one so
there is a place to put patches?
I learned on IRC that it is generally a goal not to have C++ keywords in
the
On Tue, Aug 5, 2014 at 2:04 PM, John Ralls wrote:
> Aaron,
>
> I've pulled and begun testing your guidcpp branch. It looks good, and I
> expect to merge it to master today or Thursday.
>
Excellent! :-)
> What is the motivation for compiling everything as C++ if it's still
> really C and you ha
On Aug 5, 2014, at 8:05 AM, Aaron Laws wrote:
> I've been doing some work on gnucash with relation to c++. I'm "LMAT" on
> IRC. I got the project to compile, link, and run as c++ (no .c files I'm
> pretty sure). I think it doesn't load any backends, and there are other
> problems. I had to solve
I've been doing some work on gnucash with relation to c++. I'm "LMAT" on
IRC. I got the project to compile, link, and run as c++ (no .c files I'm
pretty sure). I think it doesn't load any backends, and there are other
problems. I had to solve a problem with the module loading because c++
"mangles"
18 matches
Mail list logo
