On Tuesday, 14 April 2015 at 12:08:54 UTC, D Denizen since a year wrote:
>
> A friend has been invited to be a consultant for an investment bank that would like to build a set of analytics for fixed income products.  The team is currently quite small - about 5 C++ developers - and the idea is to start with a proof of concept and then build on it as there is further buy-in from the business.

One of the biggest issues I can think of would be code breakage. While we're the point where most compiler updates no longer break my code, if you expect to use a codebase from 2 years ago without having to update your code, you'll be disappointed.

On Wednesday, 15 April 2015 at 22:32:53 UTC, Kapps wrote:
> On Tuesday, 14 April 2015 at 12:08:54 UTC, D Denizen since a year wrote:
>>
>> A friend has been invited to be a consultant for an investment bank that would like to build a set of analytics for fixed income products.  The team is currently quite small - about 5 C++ developers - and the idea is to start with a proof of concept and then build on it as there is further buy-in from the business.
>
> One of the biggest issues I can think of would be code breakage. While we're the point where most compiler updates no longer break my code, if you expect to use a codebase from 2 years ago without having to update your code, you'll be disappointed.

In the last 2 years each breaking change I've encountered has been to close holes where latent bugs may lurk ... and often were lurking!

I welcome these breaking changes in production code.

bye,
lobo

On Wed, 15 Apr 2015 22:32:52 +0000, Kapps wrote:

> On Tuesday, 14 April 2015 at 12:08:54 UTC, D Denizen since a year wrote:
>>
>> A friend has been invited to be a consultant for an investment bank that would like to build a set of analytics for fixed income products. The team is currently quite small - about 5 C++ developers - and the idea is to start with a proof of concept and then build on it as there is further buy-in from the business.
> 
> One of the biggest issues I can think of would be code breakage. While we're the point where most compiler updates no longer break my code, if you expect to use a codebase from 2 years ago without having to update your code, you'll be disappointed.

not that anything is forcing someone to update the working compiler. i know some big codebases that still using msvc6 for the exact reason that "knowing bug is better than new bug".

On 2015-04-16 00:32, Kapps wrote:

> One of the biggest issues I can think of would be code breakage. While
> we're the point where most compiler updates no longer break my code, if
> you expect to use a codebase from 2 years ago without having to update
> your code, you'll be disappointed.

I don't agree. Every single release since at least DMD 2.050 has broken DWT.

-- 
/Jacob Carlborg