1,443 reputation
817
bio website
location
age
visits member for 3 years, 1 month
seen Oct 9 at 12:02


Aug
7
comment Why is a tooltip's attribute labelled 'title='?
@JukkaK.Korpela Fair enough, it's only the 1.2 Draft rather than specifications. However, the "title" element and attribute are historical items. The question is "Why?" The answer is "History". Also, the link between the attribute and the tag is very direct TITLE. OPTIONAL. This is informational only. If present the value of this field should equal the value of the TITLE of the document whose address is given by the HREF attribute. (from the 1.2 "draft")
Aug
7
comment Why is a tooltip's attribute labelled 'title='?
HTML 1.2 Specifications
Aug
7
answered Why is a tooltip's attribute labelled 'title='?
Jul
2
comment C# Minimal SQL Database
Are you wanting these to persist or do they only need to be in-memory?
Jun
28
comment Named output parameters vs return values
@Bobson Aah, ok. Gotcha. I had a feeling I wasn't understanding you.
Jun
28
comment Named output parameters vs return values
@JustinC Yeah, I see what you're saying, but at that point we're getting into states and such. If you're looking for a simple boolean return value, requests such as "Do", "Process", "Execute", "Run", "Set", etc. returning a simple boolean should be "true" for success. If it's possible to have multiple states (Logged but not exected, logged and executed, complete failure, etc.) then a simple Boolean value isn't what you want--you want an int/enum/state.
Jun
27
comment Named output parameters vs return values
Another example: if ProcessRequest() returns a boolean, "true" should always mean "success". Otherwise, it's just nonsensical.
Jun
27
comment Named output parameters vs return values
Yeah, if you want to return a failure condition from a function, you need to name it appropriately, so that it's clear what the return value is. DoStuff() returning a boolean would be "true" for success. FailToDoStuff() would return "true" for failure--but that's an entirely different pattern.
Jun
27
comment Named output parameters vs return values
@Bobson Neither? The question is "should it return the value or should it use the output parameter?" If the answer is "neither", you'll get no result. (Unless you store the results in some global location, which is really bad.)
Jun
27
revised Named output parameters vs return values
total rewrite of the question
Jun
27
comment Named output parameters vs return values
Well, now that edit changes things. :P
Jun
27
revised Named output parameters vs return values
took a better look at the question.
Jun
27
comment Named output parameters vs return values
So, you always use functions? What about "Try" type cases (TryResolve, TryParse, etc.) or cases with multiple outputs?
Jun
27
comment Named output parameters vs return values
But functions always return values. That's why they're functions rather than procedures/methods. When do you choose to make it a function rather than a procedure with output variables?
Jun
27
answered Named output parameters vs return values
Jun
18
comment embedding programming languages into other languages
Easy: just throw all this javascript code in a .js file and use variables declared from the server (RegisterStartupScript()). It's the same effect, just not as "inline"
Jun
4
awarded  Good Answer
May
31
awarded  Nice Answer
May
31
answered Looking for meaningful, strong argument in favor of antivirus software on development machines
May
31
comment Making Simple IF Statements Shorter
LOL. I did mention that it's my previous job, right? I'm glad that you all live sheltered lives away from the throngs of incompetent programmers and inadequate managers.