|
SHame + cOULD = SHOULD
Could says there is a choice to be made and is an element of should.
Shame on those who don't follow the implied directive is an element of should.
Should is one of the most stress-inducing words in the English lexicon and absolutely...
...ought not be used in message boxes, forms or web pages. IMNSHO
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
"I'm addicted to placebos. I could quit, but it wouldn't matter." Steven Wright yet again.
|
|
|
|
|
I think it is just local interpretation. I used to work with a guy who thought if a sentence contained the word "are" that it was then a question.
"Are you going to do that?"
"Where are you?"
He didn't have an audible response when I said.
"You are out of your mind."
So maybe in the writer's local culture, saying "should" implied "have to".
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
The software is being polite; it's anticipating users who do not like being told what to do.
|
|
|
|
|
As used in many standards documents, "should" means, "This is a best practice. You're an idiot if you don't." It is the concensus advice of the standard-writers who are usually very experienced people. It is the behavior of a very junior, very unimformed person not to treat "should" advice in a standards document as "do it". But hey, knock yourself out, do a half-assed job. That's the way to impress your boss and your customers.
I think there are people who are still rebelling against "should" advice in standards documents because they hated hearing their mom tell them what they "should" do. Chances are mom was right too.
|
|
|
|
|
Quote: Your password should contain at least 6 characters Isn't that another way of stating: "Penis" is too short ?
|
|
|
|
|
I would then expect the validator to say, "Is it in yet?".
|
|
|
|
|
serialPort1.BaudRate = 9600;
|
|
|
|
|
Sorry, you are wrong you do not get the point! The comment is for color blind.
And the variable Name Points to nothing other than COM1
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Seems rather terse, surely
serialPort1.BaudRate = 9600;
would be more helpful
|
|
|
|
|
aha
or it is british humour, which of course I like, but usually do not understand it
modified 19-Jan-21 21:04pm.
|
|
|
|
|
No; you must remember that the BaudRate property expects SI units, so the comment provides the translation to imperial units.
|
|
|
|
|
No. Its not a comment. Rather, it is commented code. This is inferred from the ; at the end.
The programmer just forgot to remove that piece of commented code.
|
|
|
|
|
I think it means:
"If you're going to muck with this setting, this (9600) was the last good one; in case I forget or die..."
|
|
|
|
|
He/she forgot to mention that this is about setting the baudrate.
|
|
|
|
|
Try this extension method:
public static T Clone<T>(this T obj) where T : ICloneable
{
return (T)(((ICloneable)obj).Clone());
}
In VB:
<Extension()>
Public Shared Function Clone(Of T As IClonable)(ByVal obj As T) As T
Return DirectCast(DirectCast(obj, IClonable).Clone(), T)
End Function
(If the VB syntax is wrong, tell me. I don't use VB any more)
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
|
No, but I found this in my code today:
public static T
Clone<T>
(
this T Connection
)
where T : System.Data.IDbConnection , new()
{
return ( new T()
{
ConnectionString = Connection.ConnectionString
} ) ;
}
I get the feeling that I never even tried to test it. I'm not sure I ever should. But it compiles!
To make matters worse, I found that because I had just written this:
public static partial class LibExt
{
private static readonly System.Collections.Generic.Dictionary<System.Type,System.Reflection.ConstructorInfo> constructors ;
static LibExt
(
)
{
constructors = new System.Collections.Generic.Dictionary<System.Type,System.Reflection.ConstructorInfo>() ;
return ;
}
public static System.Data.IDbConnection
CloneConnection
(
this System.Data.IDbConnection Connection
)
{
System.Data.IDbConnection result ;
System.Type typ = Connection.GetType() ;
if ( !constructors.ContainsKey ( typ ) )
{
constructors [ typ ] = typ.GetConstructor ( System.Type.EmptyTypes ) ;
}
result = (System.Data.IDbConnection) constructors [ typ ].Invoke ( new object [ 0 ] ) ;
result.ConnectionString = Connection.ConnectionString ;
return ( result ) ;
}
}
Which I haven't tested either.
|
|
|
|
|
Note that this only works if T has an explicit implementation of ICloneable. Otherwise, Clone() will call the instance method and not the extension method.
And you don't need the cast to ICloneable.
return (T)obj.Clone(); will do.
|
|
|
|
|
I used to generate c# switch case blocks that were about 2 or 3 pages long.
Fun times. =)
No, I won't post a sample - it's even uglier than it sounds.
It also sometimes included "goto case" statements
|
|
|
|
|
danah gaz wrote: No, I won't post a sample
Ok, I won't read your sample.
Life is a computer program and everyone is the programmer of his own life.
|
|
|
|
|
Solved
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Well it was either leave it or rewrite and debug a complex lexer by hand. The thing *worked perfectly* every single time, and was fast. It was just really, really ugly to look at.
=)
Also, I love that you're A Bastard Programmer from Hell.
I used to read the Bastard Operator from Hell series when I was a kid. Loved it.
"The power cord?" I ask
"Yes... Woopsy"
"No worries at all" I say "Is it all working well now?"
"Yes, I think so. I'm sorry, you WERE right all along"
"Yes, we're getting a lot of this, it's due to the current Global Warming
problem. It causes random thermal expansion and contraction resulting in
temperature induced movement of friction based holding mechanisms.."
I listen carefully. Nothing. In other words, <DUMMY MODE ON>...
"You can fix it permanently tho'" I say
"Really? How?"
"Well it's all to do with lowering salt deposits on the metal contacts"
"Oh!" (Dummy mode irrevocably engaged)
"All you need to do is just take the power plug out deposit some dilute mineral
salts on it. Do you have some dilute mineral salts on you?"
"Uh, no?"
"Ok, no worries, just stick it in your mouth drool into it. But make sure you
wipe the plug first to get rid of any germs, and TURN THE SWITCH OFF ON THE
MONITOR before you do - we don't want a nasty accident!
"Oh. Ok!"
>Fzzzt< >clunk!<
I hang up as the receiver hits the floor. Disk space is too good for them.
|
|
|
|
|
Yup, great stories, and nice short too
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
danah gaz wrote: It also sometimes included "goto case" statements
As well it should.
|
|
|
|
|
Yeah, I mean rolling a large DFA into a switch case is going to involve some gotos or a *lot* of duplicated code, but still, the end result looked like the stuff of nightmares. The code screamed "DON'T YOU DARE TOUCH ME!*
|
|
|
|