new bool()
-
A little pointless but not too crazy.
boolis just an alias forSystem.Boolean. Theelsewas the silly part.Boolean isOffset = new Boolean(); //default false
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = Boolean.Parse(Boolean.TrueString);Though I suspect unlike above that
trueandfalseare probably aliases for pre-defined constants. Couldn't find documentation on how they're created; above was just a guess using publicBooleanmembers. Alsotrueandfalseare operators that can be overloaded to create nullable types prior to .NET 2.0 (Nullable). Of course it's still silly to do it this way.boolis shorter to write and usingtrueandfalseis both clearer and shorter. -
A little pointless but not too crazy.
boolis just an alias forSystem.Boolean. Theelsewas the silly part.Boolean isOffset = new Boolean(); //default false
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = Boolean.Parse(Boolean.TrueString);Though I suspect unlike above that
trueandfalseare probably aliases for pre-defined constants. Couldn't find documentation on how they're created; above was just a guess using publicBooleanmembers. Alsotrueandfalseare operators that can be overloaded to create nullable types prior to .NET 2.0 (Nullable). Of course it's still silly to do it this way.boolis shorter to write and usingtrueandfalseis both clearer and shorter.Well, the whole thing could be reduced to
bool isOffset = reader["foo"].ToString().ToUpper().Trim() == "BAR";
Why couldn't the programmer see that? Why didn't someone in the 2+ years that this code has been in production fix it? Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Well, the whole thing could be reduced to
bool isOffset = reader["foo"].ToString().ToUpper().Trim() == "BAR";
Why couldn't the programmer see that? Why didn't someone in the 2+ years that this code has been in production fix it? Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
Very true! :thumbsup: I was just pointing out that
new bool()isn't as crazy as it looks at first glance :)Jon McKee wrote:
I was just pointing out that
new bool()isn't as crazy as it looks at first glanceQuite so. I don't usually even think about bool being shorthand for System.Boolean, and it's good to be reminded of the deeper nuances of the language. Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
A little pointless but not too crazy.
boolis just an alias forSystem.Boolean. Theelsewas the silly part.Boolean isOffset = new Boolean(); //default false
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = Boolean.Parse(Boolean.TrueString);Though I suspect unlike above that
trueandfalseare probably aliases for pre-defined constants. Couldn't find documentation on how they're created; above was just a guess using publicBooleanmembers. Alsotrueandfalseare operators that can be overloaded to create nullable types prior to .NET 2.0 (Nullable). Of course it's still silly to do it this way.boolis shorter to write and usingtrueandfalseis both clearer and shorter.FWIW while bool is "sort of a struct", like all primitive types instances of it are "created" (without any ctors being called) by MSIL instructions, eg `true` is created by ldc.i4.1 And `new bool()` *literally is* (not just sort of metaphysically/hypothetically according to an AS-IF rule but the literal compiler output) ldc.i4.0 I guess the moral of this story is that bool is int
-
FWIW while bool is "sort of a struct", like all primitive types instances of it are "created" (without any ctors being called) by MSIL instructions, eg `true` is created by ldc.i4.1 And `new bool()` *literally is* (not just sort of metaphysically/hypothetically according to an AS-IF rule but the literal compiler output) ldc.i4.0 I guess the moral of this story is that bool is int
-
bool isOffset = new bool();
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = true;
else
isOffset = false;I'll stop now. Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Well, look: a variable must be initialized before it can be used. Now just imagine: somehow a third possibility comes into existence which is not covered by that if ... else - now you'll run into an error when you access isOffset because it was not initialized. :^)
-
Well, look: a variable must be initialized before it can be used. Now just imagine: somehow a third possibility comes into existence which is not covered by that if ... else - now you'll run into an error when you access isOffset because it was not initialized. :^)
So you want
if (...)
...
else
...
maybe
...:laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
bool isOffset = new bool();
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = true;
else
isOffset = false;I'll stop now. Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Do you have a keyboard? Hit CTRL+A/Del and save us!
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
bool isOffset = new bool();
if (reader["foo"].ToString().ToUpper().Trim() == "BAR")
isOffset = true;
else
isOffset = false;I'll stop now. Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
bool IsOffSet = new bool { improved };
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! -
So you want
if (...)
...
else
...
maybe
...:laugh:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
Reminds me of the fuzzy logic that was so popular in the beginning of the nineties.
Wrong is evil and must be defeated. - Jeff Ello
-
Well, the whole thing could be reduced to
bool isOffset = reader["foo"].ToString().ToUpper().Trim() == "BAR";
Why couldn't the programmer see that? Why didn't someone in the 2+ years that this code has been in production fix it? Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
Well, the whole thing could be reduced to
I guess it can if reader["foo"] can never return null.
-
Marc Clifton wrote:
Well, the whole thing could be reduced to
I guess it can if reader["foo"] can never return null.
So, just for my own understanding then, something like this would be better then correct? ...
bool isOffset = (reader["foo"]?.ToString().ToUpper().Trim() == "BAR") ?? false;
Jeremy Falcon
-
Well, the whole thing could be reduced to
bool isOffset = reader["foo"].ToString().ToUpper().Trim() == "BAR";
Why couldn't the programmer see that? Why didn't someone in the 2+ years that this code has been in production fix it? Marc
V.A.P.O.R.ware - Visual Assisted Programming / Organizational Representation Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
Marc Clifton wrote:
Why couldn't the programmer see that? Why didn't someone in the 2+ years that this code has been in production fix it?
I have always predicted that this type would show up on the scene sooner or later and, by now, have seen them in action often enough. They actually do as they were told and avoided memory management at all cost. That is why they have no understanding what value types and reference types are all about, nor do they have any idea how value types are an illusion created by the compiler to spare us having to wrestle with references and check for null for every variable. To them these things make no sense and appear to be some random and arcane rules which have been inherited from languages of the past. The same goes for logical operators. I have given up on trying to help the kids when they can't get it done. They think that's more of this arcane ancient stuff that nobody needs to know anymore. Letting them figure it out themselves is the only way to convince them otherwise. So be it.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.
