I just updated guid.cpp to use boost, and I was very pleased at the
lack of explosions :-) I issued a pull request to jralls, but for
general perusal, you can see it here:
https://github.com/limitedAtonement/gnucash/commit/3dc5159cb57f25dc606416263bee8b23da3e6ffe
In Christ,
Aaron Laws
On Mon,
On Apr 27, 2014, at 7:58 PM, Mike Alexander m...@umich.edu wrote:
On Apr 27, 2014, at 5:15 PM, John Ralls jra...@ceridwen.us wrote:
However, I don’t think changing files one by one is wise: It will result in
libraries with objects compiled with different compilers, and I worry that
that
--On April 28, 2014 7:47:07 AM -0700 John Ralls jra...@ceridwen.us
wrote:
I'll make gnucash-bin.cpp after that.
Why not do it first? It needs to be done sooner or later and that
might avoid some of the explosions.
Mike
___
On Apr 28, 2014, at 8:51 AM, Mike Alexander m...@umich.edu wrote:
--On April 28, 2014 7:47:07 AM -0700 John Ralls jra...@ceridwen.us wrote:
I'll make gnucash-bin.cpp after that.
Why not do it first? It needs to be done sooner or later and that might
avoid some of the explosions.
I
--On April 28, 2014 9:04:06 AM -0700 John Ralls jra...@ceridwen.us
wrote:
On Apr 28, 2014, at 8:51 AM, Mike Alexander m...@umich.edu wrote:
--On April 28, 2014 7:47:07 AM -0700 John Ralls jra...@ceridwen.us
wrote:
I'll make gnucash-bin.cpp after that.
Why not do it first? It needs to
On Apr 28, 2014, at 10:55 AM, Mike Alexander m...@umich.edu wrote:
--On April 28, 2014 9:04:06 AM -0700 John Ralls jra...@ceridwen.us wrote:
On Apr 28, 2014, at 8:51 AM, Mike Alexander m...@umich.edu wrote:
--On April 28, 2014 7:47:07 AM -0700 John Ralls jra...@ceridwen.us
wrote:
Hi John,
in bedf00a160669a86942a1b52f47c65b8c45c9552 you said you changed LibQOF to be
compiled as C++, which you did by adding -xc++ to the CFLAGS, but leaving
the file suffixes as .c.
This isn't nice. The convention throughout all projects that I know so far is
that if the file ends in .c,
--On April 27, 2014 10:06:24 PM +0200 Christian Stimming
christ...@cstimming.de wrote:
Can we please trigger the switch from C to C++ by renaming the files,
one by one? This makes it clear which files have to adhere to C++
rules and which ones don't have to. Thanks!
I agree with this.
On Apr 27, 2014, at 2:01 PM, Mike Alexander m...@umich.edu wrote:
--On April 27, 2014 10:06:24 PM +0200 Christian Stimming
christ...@cstimming.de wrote:
Can we please trigger the switch from C to C++ by renaming the files,
one by one? This makes it clear which files have to adhere to C++
On Apr 27, 2014, at 5:15 PM, John Ralls jra...@ceridwen.us wrote:
However, I don’t think changing files one by one is wise: It will result in
libraries with objects compiled with different compilers, and I worry that
that will introduce difficult to understand bugs. That’s not a matter for
10 matches
Mail list logo
