Programmer: "Does that mean it's free?"
Cashier: stabs you in the face
this post was submitted on 01 Aug 2023
286 points (94.1% liked)
Programmer Humor
18958 readers
1068 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
Undefined behavior can go bad quickly.
Could go the other way though. Ask them nicely if they'd be willing to free up their heap of inventory, and if they return you a cart overflow, you know you've stumbled upon the ultimate zero day coupon.
I give money to cashier, change comes out of coin dispenser. I say "Looks like I won again!", cashier dies a little inside.
Every time.
Long long ago in a callcenter not too far away, I made a guy choke on his drink. As required, I asked if there was anything else he needed before I ended the call, to which he replied "the winning lottery numbers?" I said "if I had those, I wouldn't be talking to you."
Unhandled exception leads to panic
I worked in groceries story when I was younger.
But funily enough, it's probably one of the rare times I'd have answered "yes"!
We got a policy here where anything mislabelled under 10$ is free for the first item. Anything over 10$ gets a 10$ rebate.
My understanding is that it was put in place a while ago when stores stopped labelling individual items to keep them in check and ensure that consumers had a recourse in case of mistake.
Source: https://www.opc.gouv.qc.ca/en/consumer/topic/price-discount/store/tip-sheet/
NULL being "no money" by any definition, and the regular price for this probably being under 10$... well, it's probably free!
Everything is free. The problem is avoiding the cops afterwards.
can I get uhhhhh NullPointer Exception: Object reference not set to an instance of an object.
sorry we only have Exception in thread "main" java.lang.NullPointerException, is that okay?
that's how I like my coffee
How about
Class lol : Object
{
public static init void main (string args)
{
virtual void A_Start()
{
Java.Print(args)
break
}
}
}
In case it's not clear, I know nothing about Java.
When you buy these an exception is thrown.
Real world doesn't make exceptions. So you'll get UB.
It is funny, it’s just that the amount of funny is null.
Mmh nice, nullives.
Item labels only do this when they're very stressed
At least, the CSS works
null
null null null
Null null null null null? Null.
Null null NULL!
Don't try to buy it unless u want the register to open a black hole when the cashier puts it in.
Programming aside electric self edge labels are the future. Where I work we do paper labels for about 50 pretty small stores and use best part of 30,000 sheets of paper a week.
I imagine with inflation causing an increased frequency of relabeling and relabeling costs causing an increased rate of inflation, it's only a matter of time before I become too lazy to finish this joke.
600 labels per store per week. Seems like a big chunk of the inventory changes price every week, not just some tens of articles for a temporary sale.
It's more. Each a4 sheet has considerably more than 1 label on it. Most weeks there's 90-100 pages of weekly limited offer specials alone. Then every day there's large amounts of regular stock coming onto and off of special offer. Then produce is constantly being adjusted based on seasonality, the current weather (better prices on salad when it's hot etc), and to help sell through (warehouse has accepted some stock with reduced shelf life etc).
Then there's the fact the country I'm from has been experiencing food price inflation at almost 20% this year.
Wait these are new for most people? They've been around for years where I live
Free olives, the cost is listed as 0.
null != 0
Depends.
*olives > /dev/null
Isn't NULL a macro in C for 0? So doesn't that mean these items are free?
I'd guess, in context, it's a floating point price column that hasn't been set, and the table designer didn't specify the column to be NOT NULL.
I guess Rust would have solved the problem as well.
In a way it's still the same with more modern languages. Especially OOP, setting an object to Null is just setting the address pointer to to 0x00000000.
Hence NullPointerException / NullReferenceException or similar, depending on the language.
Null is zero in german - so this must be free, it's a german shop
In a country where Null literally means zero? Awesome