Take OOP class

>take OOP class
>everyone is afraid of NULL

What gives?

Attached: 1535885204738.jpg (720x669, 28K)

Other urls found in this thread:

infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
quora.com/Whats-the-difference-between-NULL-and-nullptr-in-C
twitter.com/SFWRedditVideos

what?

Math teaches us from an early age that zero is the representation of nothingness.

Attached: ASSDRIVE.jpg (720x960, 49K)

Then null would be the lack of any representation.

What the fuck even is that?

null is {} empty set
0 is the number of elements in the power set of empty set {{}}

Attached: main-qimg-6bf127a1726f305c289b14d81b3d41c4.png (602x330, 77K)

null is bad, we use maybe types now.

yeah fucked up but 0 and empty set are different

main reason is the conditional logic around it that proliferates your codebase

It's a pooper roll obviously.

That analogy is pretty good, I prefer to use a box though, 0 is an empty box and null is not having a box at all

#define NULL 0 //C++
#define NULL ((void*)0) //C

>NULL
>not nullptr
based C2x

Thing is, though, that programmers don't use null as the mathematical concept of the empty set, they use what is essentially a "typed zero" to represent something that is absent but who nonetheless has a place. Which would be a lot less confusing if Computer Programmers stopped pretending it was the empty set.

What's handfaggot?

Most things that are nullible are not Boxed Ints. Presenting the concept of 0 and Null as competing is only going to mislead amateurs and piss off experts.

infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare

Even the guy who invented null references hates them

0 is the absence of something, but we often forget what the something is.

what a bunch of tryhards holly fucking shit null is just zero end of story get you asses out of that philosophical delusion its not like you jumbobumbo shit will even be applicable because every single language has his interpretation of NULL,

The literal value of null isn't anywhere near as important as its (lack of a) type. It has huge implications for type systems.

This analogy is good, though.
You can still use 0 (the core). You can't nothing.

Securing Public Order?

ye the implications are SO BIG that the one of the oldest languages doesnt even implement the concept because its irrelevant, you are jsut a bunch of Pythagoras sitting around and discusing about noneproblems

null sounds more scary though
/dev/null > assdrive

>null is an empty box
>0 is number of items in an empty box
null is a state
0 is a number

This is the real answer

It’s a practical problem, has nothing to do with mathematics

A huge amount of bugs are caused by variables being null when they shouldn’t be, and guarding against null clutters the hell out of your code

really hate this type of construction
this means that 3∈4

>php guy hates php
>Nodejs guy hates nodejs
>Null guy hates null
Are there more brainlet IT inventions where creator realised he made a mistake?

>php
>brainlet invention
he's probably still a much better programmer then you
seriously though, groovy and scala

You obviously didn't understood what I meant.
Groovy and Scala are hated by their creators?

the dutch word for zero is nul.

The best part is the cardinality of a number is itself.

>null
>Not having an Optional type that may have a value.

Heh, plebs.

>ReadyBoost

Attached: 1499322226211.png (750x750, 443K)

what's the difference

>Math teaches us from an early age that zero is the representation of nothingness.
then a few years later we learn that zero is at the center of the number line

NULL is the 0th element of the ASCII table. It is 0.

The problem is with type safety. C++ addressed this with the creation of nullptr.

quora.com/Whats-the-difference-between-NULL-and-nullptr-in-C

You do realize that down on the machine level your retarded faggy OOP terms means jack shit and NULL literally is the same thing as 0. It's like arguing over one autist's head cannon over another's. It's fucking ridiculous and pisses me off to no end.

>down on the machine level your retarded faggy OOP terms means jack shit and NULL literally is the same thing as 0
Compilers perform a lot of reasoning that has significant effects on the end result of your program long before it ends up as machine code. Maybe you should learn the smallest bit about what you're talking about before getting this mad.

yep, that means 0 is something. and that something is nothing. if you have $0 that is a value you have. if you have - $5 you owe $5

but the null pointer has spawned millions of dumbass bugs and wasted an insane amount of time because it kicked the responsibility of checking if variables are initialized to the programmer instead of the compiler

But 0 has spawned milltions of dumbass errors and wasted an insane amount of time because it kicked the responsibility of checking if variables are 0 to the mathematician instead of the division operator

this

hello raj

This is true only for interpreted lang fags for compiled Lang's that is the same

>null is a state
>0 is a number
*blocks your path*
heh, nothing personell kid

Attached: descarga (1).jpg (225x225, 6K)

int n1 = atoi("0");
int n2 = atoi("potato");
if (n1 == n2)
{
printf("Who's fucking idea was this again?");
}