1,592 reputation
824
bio website
location Austria
age
visits member for 3 years, 11 months
seen 4 hours ago

C++


Sep
24
awarded  Autobiographer
Sep
21
revised Storing a pointer to an argument passed by (non-const) reference
added 471 characters in body
Sep
21
comment Storing a pointer to an argument passed by (non-const) reference
@stijn - of course actually telling people what is bad about these points might be much more interesting
Sep
21
comment Storing a pointer to an argument passed by (non-const) reference
+1 useful view, although I do not quite see why a (raw) pointer would signal ownership transfer
Sep
19
answered Storing a pointer to an argument passed by (non-const) reference
May
2
comment If null is bad, why do modern languages implement it?
+1 for "Because programming languages are generally designed to be practically useful rather than technically correct"
Dec
23
awarded  Notable Question
Nov
20
awarded  Popular Question
Oct
27
awarded  Yearling
Sep
18
comment Why aren't more desktop apps written with Qt?
It's funny that this question hasn't received more upvotes, given that it is really the only one actually addressing the real historical reason why "mainstream" desktop(=Windows) development did not adopt Qt. First the licensing was crap, and then, when the licensing finally caught up, people were already using .NET or were locked into their legacy MFC stuff.
Aug
3
comment Managing Multiple Projects that Share Code + Customization
Have you thought about the option of a separate "branch" (whatever TFS calls this) per client instead of a separate project?
Jul
22
accepted Does adding unit tests make sense for well-known legacy code?
May
17
accepted Is VB.NET a viable migration path for an application currently scripted in VBScript?
May
17
asked Is VB.NET a viable migration path for an application currently scripted in VBScript?
Mar
4
comment Why does automated testing keep failing in my company?
Highlight: "... It is much harder to write good testable code than just working code. " ... I'd insert "... than just good working code." It's simply harder, with no short term benefit. (Both implementations will work on shipping date.)
Feb
24
comment Handling false positives and legacy code warnings in static-analysis of C++ code?
altdevblogaday.com/2011/12/24/static-code-analysis
Feb
19
awarded  Caucus
Feb
15
comment Should I split out synchronization from my class and what's it called?
Right. shared_ptr can be written with atomics and doesn't need a mutex. Still doesn't change what I said. If you need a mutex (say because the internal mutating state is a vector), then of course you can use a per-method lock for all methods that touch that data. And that is not blocking, that's just what's necessary to keep the data consistent.
Feb
15
comment Should I split out synchronization from my class and what's it called?
And incidentally I already watched that video. Maybe twice. And I-am-not-blocking according to Herb's interpretation. Because I do not "block", I just take an internal lock for a very short time. (Just like, shared_ptr has to do for example.) And of course I can and should do it on a per method level, as long as I don't "block". (Of course in the specific case of my m_state above I could have used an atomic, but that not always possible when method-internal sync is appropriate.)
Feb
15
comment Should I split out synchronization from my class and what's it called?
So is it called a Monitor then?