1,100 reputation
622
bio website yourcodeisshowing.wordpress.c…
location Quebec City, Canada
age 37
visits member for 4 years, 2 months
seen Oct 27 at 18:55

Developer with 8 years experience. I work with J, C, C++, C#, SQLite, MySQL, VBA, and a bunch of other odds and ends.

On Twitter: @MPProg


Feb
25
awarded  Scholar
Feb
25
awarded  Critic
Feb
25
accepted Constructor parameter validation in C# - Best practices
Feb
25
comment Constructor parameter validation in C# - Best practices
Sorry, this is just too much of an anti-pattern to consider.
Feb
24
comment What did your college do right and what could they improve upon?
@zneak: :) Human communication. I can do P2P from home, thank you very much.
Feb
23
revised What did your college do right and what could they improve upon?
Added remote teaching
Feb
23
answered What did your college do right and what could they improve upon?
Feb
23
comment Constructor parameter validation in C# - Best practices
@ChaosPandion: Maybe not specific, but definitely strongly biased. Tagged nonetheless as suggested.
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott Updated. I think you've hit something on the head there. The more I think about it, the more that specific context was necessary. Thanks again for clearing things up!
Feb
23
revised Constructor parameter validation in C# - Best practices
added 563 characters in body; edited tags; edited title
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott What @Chad said. There were two cases of the validation in the calling class, which were identical. Even if they were combined, the rule for the class is that the argument cannot be null. It made sense to suppose that the class itself should manage this. Now it's encapsulated, nearly forgotten.
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott For my defense, the pre-validation bit wasn't my creation :) I just raised an alarm because it was duplicated.
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott I see. Forgive me for not understanding what you meant. The alternative which incited me (I wouldn't say forced) to ask the question is that the parameters were pre-validated, before instanciation. On failure, a message would be shown, and the constructor was never called.
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott For fear of repeating myself, I was open to the possibility of there being some other approach, which I did not know. I believe I'm not all knowing, that much I know for sure.
Feb
23
comment Constructor parameter validation in C# - Best practices
@S.Lott I'm a humble programmer, I know there's always something else to learn, so that I'm open to the idea of some other doodad for this sort of thing, even if seemingly unlikely. I actually read somewhere that constructors should never fail (which is admittedly bull...)
Feb
23
comment Constructor parameter validation in C# - Best practices
+1 for the confession alone :)
Feb
23
asked Constructor parameter validation in C# - Best practices
Feb
20
answered Are there any downsides of 2 developers getting married?
Feb
1
awarded  Commentator
Feb
1
awarded  Teacher