|
honey the codewitch wrote: jmaida's axiom: S=P+1
That assumes that a parachute is used only once.
A better formalism would be:
WP, NS are non-negative integers.
WP = number of working parachutes
NS = number of sky dives
NS = 0
do
NS = NS + 1
while (WP > 0)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Happy Birthday!
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
You probably have been up since 3 have a Good one Paul
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Best wishes ... and for many more years showing the rest of us how it should be done.
|
|
|
|
|
Happy birthday!
|
|
|
|
|
49th birthday?
Again?
|
|
|
|
|
That ship sailed a long time ago!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
~ ~
* * * *
* *
~ * * ~ *
* ~ * * ~
) ( ) *
* ~ ) (_) ( (_) ) (_) ( *
* (_) # ) (_) ) # ( (_) ( # (_) *
_#.-#(_)-#-(_)#(_)-#-(_)#-.#_
* .' # # # # # # # # # # # `. ~ *
: # # # # # # # # :
~ :. # # # # .: *
* | `-.__ __.-' | *
| `````"""""""""""````` | *
* | | ||\ |~)|~)\ / |
| |~||~\|~ |~ | | ~
~ * | | *
| |~)||~)~|~| ||~\|\ \ / | *
* _.-| |~)||~\ | |~|| /|~\ | |-._
.' '. ~ ~ .' `. *
: `-.__ __.-' :
`. `````"""""""""""````` .'
`-.._ _..-'
`````""""-----------""""`````
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
Happy birthday...they come faster and faster don't they?
|
|
|
|
|
Does that mean the presents do as well?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
As you get older the presents get fewer because;
- Nobody knows what to get an old fart
- They figure you have everything already
- You're to old to enjoy stuff
Or in my case;
- That grouchy old man don't deserve nothing
- I don't want to deal with that old grouch
Have a great birthday man!
|
|
|
|
|
Happy Birthday! And, many more!
|
|
|
|
|
Happy Birthday Paul. I hope you had a nice day.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Is all I can say
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
Official congratulations!

|
|
|
|
|
|
It's Hell getting old!
But you keep it up.
And Happy Birthday to you.
The good guys need to stick together!
|
|
|
|
|
Happy Birthday Paul!
|
|
|
|
|
Remember:
Time is not your enemy;
Gravity is.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
There was some piece of C# code I am refactoring (+ fixing small bug) where, at some stage, an expression like a.b.c is replaced by (private method) GetBc(A a) . When I refactored that, I ignored GetBc(a) and wrote a.b.c instead, because I like it better that way.
One of the code reviewers complained I was not using GetBc(a) . Whatever, I updated my code to use GetBc(a) again. Now I wonder, mm.. how many people would care about that kind of detail and what kind of expression they would prefer?
|
|
|
|
|
How would that work?
GetBC(A a) => (a.b, a.c);?
GetBC(A a) => new { a.b, a.c };?
In both cases I'd prefer a.b.c.
I don't see the added value of GetBC
|
|
|
|
|
C GetBc(A a) => a.b.c;
The only "real advantage" (in the day of yore before intellisense) is that it's more like
SomeClass GetBc(AnotherClass a) => a.LongPropertyName.OtherLongPropertyName;
|
|
|
|
|
Super Lloyd wrote: C GetBc(A a) => a.b.c; This is just ridiculous
Send that reviewer over to this thread so he can read that I find him ridiculous.
Judging from the other replies on this thread I'm not the only one
Super Lloyd wrote: The only "real advantage" (in the day of yore before intellisense) is that it's more like In those instances I don't make a function, but I simply use a variable.
var shortName = a.LongPropertyName.OtherLongPropertyName;
|
|
|
|
|
In most cases it's ridiculous, yes. It's not a construct I think I've used myself. However...
What if b is null? Suppose b is a lazy-loaded property which is only instantiated as/when referenced, but a does not support that functionality? Or - in the circumstances where you use the GetBC function you need a default value returned if b or c are null.
I'd agree that if GetBC does nothing more than return b.c then yes, it's pointless; but if there's code in that function (even just exception handling) then maybe... though a more descriptive/specific name than simply GetBC might be appropriate.
|
|
|
|
|
I take the liberty to slightly defend that code reviewer. It is a matter of blackboxing: When you reference that bc property of a, you should be unaffected by how the a object structures its attributes, i.e. whether it has a single bc attribute (and maybe bc1, bc2, bc3, ...) or groups all the b<*> attributes into a b object with subfields.
C# lets the a object provide a .bc property, so that is can map it to a .bc or a b.c field at its own discretion. Maybe that is nowadays available in C++ as well (it wasn't when I switched from C++ to C#). I have become very fond of blackboxing and need-to-know: You should need to know as little as possible about the inner structure of the objects you interact with. a.b.c does reveal an inner structure that you shouldn't care about.
But I most certainly would prefer a .bc property to a GetBc(A a) method!
|
|
|
|