Patrick

Antwerp, Belgium

none

Age: 51

Die-hard developer.
Not afraid to go low-level (even down to assembly when needed during debugging).
Prefers readable code over short, complex, 'would-be-smart', unreadable code.
Musical preferences: EBM (Front 242), Synthpop (Human League, Heaven 17), Electronic stuff (Kraftwerk) and most things that don't fit mainstream (Severed Heads, Isao Tomita).
Likes 80's pinballs (Comet, High Speed)

Jan
29
awarded Nice Question
Jan
22
awarded Famous Question
Dec
28
awarded Notable Question
Dec
18
asked File deleted with remove function still shows up in FindFirstFile/FindNextFile loop immediately following the removal. Why is this?
Nov
8
accepted How to prevent use of variable after its value has been moved to another variable?
Sep
20
awarded Popular Question
Sep
15
awarded Nice Answer
Sep
2
answered Is using a non-ptr at std::map's value a good practice
Sep
2
answered Why the memory not freed in top and pmap?
Aug
30
answered How to pass an object's address on the heap from a function using a pointer
Aug
26
awarded Yearling
Aug
26
awarded Yearling
Jul
28
asked How to prevent use of variable after its value has been moved to another variable?
Jul
22
comment When is the compiler allowed to optimize auto+brace style initialization?
@CoryKramer: Visual Studio 2015 now correctly handles the =default move constructors. Hooray.
Jul
22
comment When is the compiler allowed to optimize auto+brace style initialization?
Visual Studio 2015 is indeed giving an error on this (Product::Product(Product &&)': attempting to reference a deleted function). So it was clearly a bug in Visual Studio 2013.
Jul
22
comment When is the compiler allowed to optimize auto+brace style initialization?
Just checked Visual Studio 2015: here an error is given (which is correct): error C2280: 'Product::Product(Product &&)': attempting to reference a deleted function
Jul
21
answered C++: How to find out "unused" classes starting from known "point"
Jul
10
asked How to find the Skype for Business command line options?
Jul
1
accepted When is the compiler allowed to optimize auto+brace style initialization?
Jun
28
comment When is the compiler allowed to optimize auto+brace style initialization?
This is not correct. According to the standard the compiler must first construct a temporary, then move-construct it into the variable. But the compiler is allowed to optimize this (constructing the variable directly), provided the logical effect would be the same as construction+moveconstruction, which is not the case if the moveconstructor is deleted.
1 2 3 4 5