|
And valleys park your car for you.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
|
Yeah, right. Griff is just upset he didn't think of the mountain line first.
|
|
|
|
|
This thread has peaked my interest.
/ravi
|
|
|
|
|
And a small, narrow river is just a stream
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Oh, come on!
You're Dutch, so your idea of a mountain is already a joke!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
Seriously, I saw taller staircases!
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Vaalserberg 4 life!
~323m of pure awesomeness!
I've never actually been there
|
|
|
|
|
These are the effects of legalized pot...
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
Meat kettle.
Software Zen: delete this;
|
|
|
|
|
I winced so hard that I might have thrown my back out.
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
We had a deal where you would make me funnier, smarter, and a better dancer... I saw the video... we need to talk.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
That is sooooo funny... As it was 12 yeas ago
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
I was going to post an early version but it was in ancient greek and didn't think anyone would understand.
New version: WinHeist Version 2.2.2 Beta I told my psychiatrist that I was hearing voices in my head. He said you don't have a psychiatrist!
|
|
|
|
|
Oh, I'm sure some know-it-all here on the site, speaks fluent ancient Greek.
|
|
|
|
|
... maybe if you translated it to ancient Geek...
"It was when I found out I could make mistakes that I knew I was on to something."
-Ornette Coleman
"Philosophy is a study that lets us be unhappy more intelligently."
-Anon.
|
|
|
|
|
A few beers and I'll translate hieroglyphics for you, no problem.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
You obviously hadn't had enough to drink when you watched it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Clause 8.2.1.C of the deal specifies that you are permitted to review recordings of your own actions while you were under the influence, only while you're under the influence.
Meaning, you're welcome to watch that video or have that chat, but not until you'll down a few pints.
|
|
|
|
|
So a coworker just called me and was "you have got to see this!"
Basically, he just invoked a method with some named parameters (of which two were unevaluated LINQ expressions) and the invoked method receives the parameters in the wrong order.
Parameter a gets expression b while parameter b gets expression a.
We tried evaluation the LINQ expressions first, but the result was the same.
Then we removed the names from the parameters and everything worked fine.
We also tried to make the parameters named and go down a .NET version (to 4.5.2), but the problem still persisted.
We checked the intermediate language and, indeed, the variables were loaded onto the stack in the wrong order.
What the...
Moral of the story, don't use named parameters as they are bugged
Example:
Just a regular method call, be it a bloated one.
public SomeClass SomeFunction(Input input)
{
SomeType outA;
AnotherType outB;
ThirdType outC;
return somefield.DoSomething(
name1: input.Field1,
name2: input.Field2,
name3: input.Field3,
name4: input.SomeCollection.SelectMany(...).Where(...).Select(...),
name5: input.AnotherCollection.Select(...),
name6: out outA,
name7: out outB,
name8: out outC
);
} I know that code ain't pretty, but somefield.DoSomething was code that was generated from an Oracle package, so yeah.
That's also why it's named, so the parameters won't mix up when someone changes the package.
modified 1-Dec-16 14:08pm.
|
|
|
|
|
Post an example
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Updated my post with an example, just some pseudo code.
There's not much to see anyway, .NET just mixes up two variables
|
|
|
|
|
Why are you using named parameters? They use more stack space than standard parameter passing, and therefore performance suffers. IMHO, they also have no tangible benefit with regards to code readability.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 1-Dec-16 13:35pm.
|
|
|
|
|
John Simmons / outlaw programmer wrote: They use more stack space than standard parameter passing, and therefore performance suffers. Don't think so, naming them is just some syntactic sugar.
Anyway, they were named because the method being called was some code generated from an Oracle package.
When the Oracle package changes so does the code, so by naming the parameters they're not messed up (well, apparently they are ).
|
|
|
|