2,401 reputation
1819
bio website arcsynthesis.org/gltut
location Los Angeles, CA
age 37
visits member for 2 years, 10 months
seen Aug 23 '13 at 12:49

I am a game developer with a fairly broad knowledgebase in the fields of animation and graphics, with a touch of AI.

Projects:


Oct
26
answered What's so difficult about SVN merges?
Oct
26
awarded  Organizer
Oct
26
revised What's so difficult about SVN merges?
edited tags
Oct
26
asked Software licensing and code generation
Jun
20
awarded  Nice Answer
Jun
20
awarded  Yearling
Jun
11
comment How to manage a developer who has poor communication skills
@Jason: 'Maybe the other "average" programmers would become "above-average" if given more programming work, future projects would get done even faster.' And maybe they won't. There's no way to know for certain. So why risk throwing away a valuable asset on the hopes that others will pick up the slack?
Feb
19
comment Why is it so difficult to make C less prone to buffer overflows?
It's still the responsibility of programmers to use the tools they have now to fix these problems. Take a half-day or so and do some grepping through the source code for these things.
Feb
19
comment Why is it so difficult to make C less prone to buffer overflows?
+1 for aiming the problem on the programmers, not the language.
Feb
17
comment Why are several popular programming languages influenced by C?
@DeadMG: But the question is about syntax. You can consider the syntactic similarities to be irrelevant, but the person asking the question wants to know why these irrelevant similarities exist.
Feb
12
awarded  Autobiographer
Feb
7
awarded  Nice Answer
Feb
7
awarded  Good Answer
Feb
7
awarded  Nice Answer
Feb
6
comment Is C++11 Uniform Initialization a replacement for the old style syntax?
@RobertDailey: "if you did int foo(10), would you not run into the same problem?" No. 10 is an integer literal, and an integer literal can never be a typename. The vexing parse comes from the fact that Bar() could be a typename or a temporary value. That's what creates the ambiguity for the compiler.
Feb
6
comment Is C++11 Uniform Initialization a replacement for the old style syntax?
@RobertDailey: They don't all turn into initializer list statements. as I said, the only reason vector<int> fails is because the type of the initializer list is int, which conflicts with the constructor that takes a single int. So it would only be a problem in those specific circumstances. And, as Xeo points out, you can easily use a simple placeholder object as a way of differentiating between those containers.
Feb
6
comment Is C++11 Uniform Initialization a replacement for the old style syntax?
@JohannesSchaub-litb: Fixed.
Feb
6
answered Is C++11 Uniform Initialization a replacement for the old style syntax?
Feb
6
comment Is C++11 Uniform Initialization a replacement for the old style syntax?
This might be a subject better discussed on Programmers.se. It seems to lean towards the Good Subjective side.
Feb
5
comment std::shared_ptr as a last resort?
let us continue this discussion in chat