For the English Language masters...
-
I've never personally needed to learn any rules about this - I've always been right on instinct ever since I was very little. However, this looks like it knows what it's talking about.[^] At the end, it says, "Use i before e except after c or when sounded like a as in neighbor or weigh; and except seize and seizure and also leisure, weird, height, and either, forfeit, and neither."
"What am I in the eyes of most people, a nonentity, an eccentric, or an unpleasant person--somebody who has no position in society and will never have; in short, the lowest of the low. All right, then--even if that were absolutely true, then I should one day like to show by my work what such an eccentric, such a nobody, has in his heart."
Ravel H. Joyce wrote:
I've always been right on instinct
ALWAYS? Thats quite a boast, even Einstein said he was wrong once! (ok he was wrong when he mis-corrected what was already right about his special theory, he soon corrected it back :) )
------------------------------------ I try to appear cooler, by calling him Euler.
-
Sadly this rule isn't sufficient either, to be honest, you could try in vein to work out standardised rules - The English language is somewhat weird and inconsistant, probably due to the kaleidoscopic way it's been merged from various sources, since ancient times most of our European neighbours have invaded at some point or other, and the language reflects that with many foreign influenced words. Science tends not to play by the rules either. You could probably do with some caffeine by now, I'm sure!
-- Help me! I'm turning into a grapefruit! Buzzwords!
benjymous wrote:
inconsistaent
:)
-
Ravel H. Joyce wrote:
I've always been right on instinct
ALWAYS? Thats quite a boast, even Einstein said he was wrong once! (ok he was wrong when he mis-corrected what was already right about his special theory, he soon corrected it back :) )
------------------------------------ I try to appear cooler, by calling him Euler.
Yes, always. ;P
"What am I in the eyes of most people, a nonentity, an eccentric, or an unpleasant person--somebody who has no position in society and will never have; in short, the lowest of the low. All right, then--even if that were absolutely true, then I should one day like to show by my work what such an eccentric, such a nobody, has in his heart."
-
Yes, always. ;P
"What am I in the eyes of most people, a nonentity, an eccentric, or an unpleasant person--somebody who has no position in society and will never have; in short, the lowest of the low. All right, then--even if that were absolutely true, then I should one day like to show by my work what such an eccentric, such a nobody, has in his heart."
I like your Confidence! :-D
------------------------------------ I try to appear cooler, by calling him Euler.
-
I like your Confidence! :-D
------------------------------------ I try to appear cooler, by calling him Euler.
I like your praise!
"What am I in the eyes of most people, a nonentity, an eccentric, or an unpleasant person--somebody who has no position in society and will never have; in short, the lowest of the low. All right, then--even if that were absolutely true, then I should one day like to show by my work what such an eccentric, such a nobody, has in his heart."
-
So, I'm Swedish and have some difficulties to differ between "insure" and "ensure". When coding, I tend to use "ensure" as in the function
void EnsureProperState()and in the comment// Ensures that nothing bad will happen with bla bla bla.To me "insure" is about physical insurance, like "life insurance" or "vehicle insurance". Is there a more strict difference between them?-- Time you enjoy wasting is not wasted time - Bertrand Russel
-
Use "make sure" instead of "ensure". That way you'll never go wrong and you don't have to remember all those prefixes. Example:
int i, e; i = i; // make sure that i is i e = e; // ... and e is e:)Well, that doesn't fit into my way of naming functions:
MakeSureXYZ()would in my world mean that aSureXYZobject will be somehow "made" by that function, whereasEnsureXYZ()cannot be misunderstood. :)-- Time you enjoy wasting is not wasted time - Bertrand Russel
-
So, I'm Swedish and have some difficulties to differ between "insure" and "ensure". When coding, I tend to use "ensure" as in the function
void EnsureProperState()and in the comment// Ensures that nothing bad will happen with bla bla bla.To me "insure" is about physical insurance, like "life insurance" or "vehicle insurance". Is there a more strict difference between them?-- Time you enjoy wasting is not wasted time - Bertrand Russel
You are correct sir.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001 -
You are correct sir.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Gosh! I'm flabbergasted! I've never been "sir"-ed before... :rolleyes:
-- Time you enjoy wasting is not wasted time - Bertrand Russel
-
Well, that doesn't fit into my way of naming functions:
MakeSureXYZ()would in my world mean that aSureXYZobject will be somehow "made" by that function, whereasEnsureXYZ()cannot be misunderstood. :)-- Time you enjoy wasting is not wasted time - Bertrand Russel
