On Thursday, 24 December 2015 at 17:20:02 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 14:48:46 UTC, John Colvin
wrote:
Often when you see breakage it's the compiler actually
enforcing a pre-existing rule that the code in question broke.
So that made me think, there is any flag that I
On Thursday, 24 December 2015 at 17:17:39 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 16:05:18 UTC, bachmeier wrote:
But 2.060 was released in 2012...
Yes I know it's old but and the reason was to avoid breakage
that already had happened before.
I know that sometimes this
On Thursday, 24 December 2015 at 16:05:18 UTC, bachmeier wrote:
But 2.060 was released in 2012...
Yes I know it's old but and the reason was to avoid breakage that
already had happened before.
I know that sometimes this (Breakage) is inevitable as the
language grows, but my concern here is
On Thursday, 24 December 2015 at 14:48:46 UTC, John Colvin wrote:
Often when you see breakage it's the compiler actually
enforcing a pre-existing rule that the code in question broke.
So that made me think, there is any flag that I could turn on,
and pass by over those errors?
JerryR.
On Thursday, 24 December 2015 at 17:20:02 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 14:48:46 UTC, John Colvin
wrote:
Often when you see breakage it's the compiler actually
enforcing a pre-existing rule that the code in question broke.
So that made me think, there is any flag that I
On Thursday, 24 December 2015 at 17:17:39 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 16:05:18 UTC, bachmeier wrote:
But 2.060 was released in 2012...
Yes I know it's old but and the reason was to avoid breakage
that already had happened before.
I know that sometimes this
On Thursday, 24 December 2015 at 13:16:02 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 05:50:06 UTC, Israel wrote:
On Thursday, 24 December 2015 at 04:06:40 UTC, JerryR wrote:
A couple of months ago, I decided to upgrade my DMD to a new
version: 2.066, and today I needed compile that
On Thursday, 24 December 2015 at 05:50:06 UTC, Israel wrote:
On Thursday, 24 December 2015 at 04:06:40 UTC, JerryR wrote:
A couple of months ago, I decided to upgrade my DMD to a new
version: 2.066, and today I needed compile that project again,
which a year ago I had compiled with DMD 2.060.
On Thursday, 24 December 2015 at 13:16:02 UTC, JerryR wrote:
On Thursday, 24 December 2015 at 05:50:06 UTC, Israel wrote:
On Thursday, 24 December 2015 at 04:06:40 UTC, JerryR wrote:
[...]
Upgrading GTKD is definitely the best route...
...you wont have to fix anything on the library's side.
A couple of months ago, I decided to upgrade my DMD to a new
version: 2.066, and today I needed compile that project again,
which a year ago I had compiled with DMD 2.060.
Now if you look below you will see the errors that I'm getting
with changing from DMD 2.060 to 2.066, and all the errors
On Thursday, 24 December 2015 at 04:06:40 UTC, JerryR wrote:
A couple of months ago, I decided to upgrade my DMD to a new
version: 2.066, and today I needed compile that project again,
which a year ago I had compiled with DMD 2.060.
[...]
Upgrading GTKD is definitely the best route. Most
11 matches
Mail list logo
