3,810 reputation
1537
bio website heinzi.at
location Vienna, Austria
age 34
visits member for 3 years, 4 months
seen 2 days ago

Dec
14
comment When to use .ToString() when concatenating a string in C#?
Side note: In VB.NET, this ambiguity is avoided by having an explicit string concatenation operator: "Expression: " + a will throw a compile time error (with Option Strict On), "Expression: " & a will perform string concatenation.
Nov
19
asked Provide web images with high resolution and let the browser scale it. A bad idea?
Sep
28
awarded  Nice Question
Aug
28
awarded  Good Answer
Aug
9
awarded  Yearling
Jul
2
awarded  Curious
May
3
awarded  Announcer
Apr
28
comment Static linking with modified LGPL code
@TacB0sS: It means that if you statically link MyApp.obj to SomeLgplLibrary.lib to create MyApp.exe, you need to provide MyApp.obj, so that the user can replace SomeLgplLibrary.lib with SomeCompatibleLgplLibrary.lib and re-link MyApp.exe.
Apr
28
comment Static linking with modified LGPL code
@TacB0sS: "(not necessarily source)" applies to your application, whereas "has the opportunity to modify" applies to the library.
Apr
19
comment What is meant by a primitive data type?
...and the wink illustrates the (obvious) implication that his definition of a primitive type is not particularly in the context of C#.
Apr
19
comment What is meant by a primitive data type?
@barlop: My comment starts with "Then...", so please read it in context: Josh said that by his definition, C#'s int is not a primitive type, and I replied that, in that case ("then"), none of C#'s types were primitive, since none meets his definition of primitive.
Mar
19
awarded  Nice Question
Feb
7
awarded  Notable Question
Jan
29
comment Are classes with only a single method a problem?
Related (almost a duplicate): programmers.stackexchange.com/q/175070/33843
Nov
21
comment Dictionary of objects
Due to floating-point inaccuracies, I'm not sure if double is a wise choice for a dictionary key.
Nov
12
comment In retrospect, has it been a good idea to use three-valued logic for SQL NULL comparisons?
@DanielB: That was exactly the point of my question: From a mathematical point of view, it all makes perfect sense. However, from a practical point of view, does it really make life easier for developers?
Nov
10
accepted In retrospect, has it been a good idea to use three-valued logic for SQL NULL comparisons?
Nov
7
comment In retrospect, has it been a good idea to use three-valued logic for SQL NULL comparisons?
PS: I know that this borders on "too broad" and "opinion-based", but I've tried to make it as answerable as possible. It is not meant as a rant, but as a genuine question.
Nov
7
asked In retrospect, has it been a good idea to use three-valued logic for SQL NULL comparisons?
Nov
4
revised IL and case-sensitivity
added 275 characters in body