Well that depends I think wether its a local variable or an instance variable. At least if my memory doesn't fail to serve me.
Local variables aren't initialized on declaration, but is unassigned a value?
zamies
@zamies
Best posts made by zamies
-
RE: Overheard in the next cube
Latest posts made by zamies
-
RE: Windows Vista Ultimate Edition Pricing WTF
its 549 euro's here on the old continent, perhaps i'll order it in the us?
-
RE: Please destroy our system now
@mhughes said:
This shows a very common mistake people make.
When
reporting a problem, just report the problem. Don't give possible
causes, or possible solutions. Just report the damn problem.
"Dear IT,
I
get a message on my machine every few mintues saying SYS is out of disk
space. I don't store anything there. Please fix this.
-User"
Giving possible solutions or causes in the initial contact will only complicate things.
This
goes for most request-for-help things. Cable companies, electric
companies, doctors, IT, your bank, etc. Sure you might go
through some mindless questions, but you are more likely to get your
problem fixed.
Well that's a nice thought. I will give that heuristc a go, and see if it works.
-
RE: Delphi version 7 WTF
@phithe said:
Well yes, there are workarounds. What I ended up doing was using an array of TStringLists.
My point is, it should have been so much simpler.
Yeah meddling with pointers is soooo much more simpler, and so less bug prone...
-
RE: Anaconda
@PhillS said:
What I don’t get is why this happened two times
in a row on my installations of Fedora Core, but has never happened on
any of my other Linux installations (and I’ve tried about four *nix
distros - Gentoo, CentOS, Ubuntu and FreeBSD).
ahum...
-
RE: VB WTF
@jsmith said:
@RiX0R said:
My shot:
In CallMe a, the variable a is passed by reference as you would expect. In CallMe (a), (a) is first evaluated as an expression, because of the parentheses, then the result of that expression is passed by reference... yielding no change in the variable if the value is changed.
Though why it would be legal to pass an expression by reference, I don't know.
Bingo. (a) is seen as an expression, so it cannot be successfully passed by reference. I can answer your why question too -- backwards compatibility. In VB6 and earlier, there is only one rule for using parentheses on calls:
I think it is a little bit different the expression can be passed by reference but is something else then teh variable a. So while the expression changes value a is left unchanged so two times 6 is printed to the screen. I must say that with a ridiculous rule like that you're making life for the programmer extremely difficult.
One of the biggest WTF's of VB <.net in my opinion is that de default parameter passing is byRef.
-
RE: Overheard in the next cube
Well that depends I think wether its a local variable or an instance variable. At least if my memory doesn't fail to serve me.
Local variables aren't initialized on declaration, but is unassigned a value?