I propose a new, more threatening kind of control flow.
do { /* something */ } or else { /* you don't want to find out */ }Some C++ style guides suggest the following naming convention for functions that crash on any error
OpenFileOrDie()PHP has the always wonderful (and perfectly functional) syntax of
logUserIn() or die();Or Perl
Perl also has
unless()for the very purpose in OP, which is a more sensible choice.Oh, and if you need to reinforce your belief that Perl is a mess, the single-quote character can be used as a package separator instead of “::”. This was set in the 90s when nobody was quite sure of the right syntax for package separators, so it borrowed “::” from C++ and the single quote from Ada (I think).
That means the
ifn't()in OP can be interpreted as calling thet()function on theifnpackage.The “::” separator is vastly preferred, though. Single quotes run havoc on syntax highlighting text editors (since they can also be used for strings). About the only time I’ve seen it used is a joke module,
Acme::don't.Where do you think PHP stole it from?
Bash?
Personally, I like to call catched exception variables
up, so for a rethrow I canthrow up;.Except rethrowing an exception in C# is just
throw;, anything else is a crime against the person who reads your stacktraces.
One of the modules in a project I’m working on is called
VulkanOrDiewhich always makes me crack up when I see it in the compilation messages.I mean, it makes sense to call ComplainToErrorAndExit just ‘die’, no?
It’s funnier when you try to SysCallAndDie() :-P
(that’s a real thing in perl btw - I guess that function didn’t get the memo)
Now what about GZDoom’s
GoAwayAndDie();?
this is just a menacing try/catch!
It_would_be_a_shame_if(condition)
The better try-catch. More intuitive if you ask me.
It exists, kind of. Python has this construct
for item in iterable: ... else: ...which always puzzles me, since it depends on a break statement execution. I always have to look it up when the else block is executed.
You just made me a offer I can’t refuse. I go now to sleep with the fishes…
do { /* something */ } do hast { /* something */ }do { /* something */ } do hast { /* something */ } do hast mich { /* something */ }
Please God let this be a humorous post that somehow does not also find a way to manage to come true…
deleted by creator
i mean, “unless” tends to be the usual term for an “if not” keyword in languages that implement such a thing
Which is awful and incredibly confusing. I hate ruby
And Perl
And my axe!
totally agree; just saying that if it’s GOT to be something, that something should probably be unless… unless . . .
I find that you need to choose carefully when to use it. Simple cases tend to be alright. Larger, more complex conditions shouldn’t touch it.
Yeah, to be clear, I don’t like it, I don’t like it one bit:-P.
If not anybody have time for that.
*ifn’t*
Oh dear Lord what have I done!? :-P
deleted by creator
cap () {
}
nocap () {}
nocap(frfr){
}
Reduce exclamation marks!? Great Scott!!! Is there a shortage of punctuation in the future!?
You could have saved two, all you had to do was use the interrobang. You’re a monster.
All known deposits were depleted
1.21GB!!!
Kernighan, what was I thinking?
deleted by creator
unlessn’t
I’m sorry, I hate the “unless” so much
At one of my first jobs, I was tasked to rewrite a bunch of legacy Perl scripts in Python and the unless lines always made me trip up. I don’t know why but it really messed with my mental flow when reading Perl code
Basic used “else”.
It’s nice. “if”, “then”, and “else”. I spent a year programming a shitty roulette game on an Apple 2e back in high school. I still remember the joy of using if/then/else paired with goto to make a horrible mess of spaghetti logic.
But yeah, “else” is nice.
Using a standalone ‘else’ would tickle my brain in the same nice way that being able to declare a variable inside an ‘if’ statement as if it were a ‘for’ loop (which you can do in modern C++) does.
Or a rust “if let”
Ooh yes. Rust is king when it comes to this sort of inline stuff. Inline
match. Mmmmmm!
Many languages let you scope variables.
In c# you can create an arbitrary scope to declare variables in. Most likely in others as well.
Ah clever, didn’t think of doing this. Not having to encapsulate if statements in scopes would still look cleaner though
It’s handy if you’re creating temp variables for single use that you don’t need to use again.
Although I admit I’ve only ever done it a couple times lol
Again in c# you can omit the scope and only the next statement is part of an if or loop.
Block scoped variables are bad?
🤷♂️
Let’s just scrap every language except various forms of BASIC.
Please God, no. I had to unravel terminal scripting code that was written in some propriety BASIC language with basically no documentation.
Took me a chunk of time trying to figure out how it worked before I made the realization that it was BASIC
Try PL/SQL.
I haven’t written any Ruby for years, but I still praise it in every conversation I have regarding programming languages. It’s basically a much simpler Python, with some design ideas that are both beautiful and deeply strange.
Ruby was designed to evoke joy and they absolutely succeeded. Usually, programming is mostly a means to an end to me. But using Ruby just feels so amazing, it’s almost impossible to even describe to somebody who has never used it before.
The Perl version of it is even greater!
aint (something) { somethingElse() }As a Virginian learning coding, this would make my damn day.
#define aint(x) if (!(x))
Or maybe
taint(condition) {}
ifn't(!valid)halp?I believe that resolves the same as
ain’t!(!untrue)
Removed by mod
{ put(a, "heartache") tell(me, "why") ain't(nothing) { put(a, "mistake") //... } }
Why not just ifnot? Same count of characters but an o instead of a possibly problematic single quote.
I think it’s just capitalizing on a trend to add n’t to otherwise noy contractions, to make them into contractions. Contractionn’ts, if you will
Yes… how is “reducing exclamation marks” a good thing when you do it by adding a
'(not to be confused with,´,‘or’` …which are all different characters).Does this rely on the assumption that everyone uses a US QWERTY keyboard where
!happens to be slightly more inconvenient than typing'?If someone really wanted to add it, probably the best would be to use
unlessI really liked having
unlessin Ruby; a!can be easy to miss, whileunlessmade it clear without needing to write out!= true.It’s also cool when you do unless(!condition). I particularly like this.
Still not as good as
whenceIs this a reference to something because I’d love to read it if you have a time to share.
Woah. I did a quick google and it’s not just a meme, but actually used in some major lang’s libraries.
This is one of those “modern Google/search sucks” moments because I couldn’t immediately find examples of it in a programming language.
I actually used DDG and most I’ve seen, they’re just used as arguments for functions notably in C and Python
It is used in
kshkorn shell to see what executable responds to a command:https://superuser.com/a/351995
Edit: Oh, what a rabbit hole: Why not use “which”? What to use then?
Legislation (which feels similar to programming languages sometimes) seems to have some keywords of its own. I remember seeing a lot of
Whereas ...andHaving regard to ....
“Help’s with readability”? You know what else helps? Not using contractions and introducing an unbalanced single quote.
If they’d’nt’ve done that, it’d’ve been better. Agreed.
Aside: rip Tom Scott
TIHI
Runs havoc on parsing, too. It’s bad for both humans and robots. I say we ship it.
This feels racist against Appalachia. We naturally speak with contractions and are commonly referred to as “unbalanced”.
I’m struggling to understand if this is true or ifn’t true
Imagine the regex needed to highlight code with that extra single quote.
I’d take a
notor “if not” operator tbh.It has a not keyword it’s used for pattern matching.
if (x is not null)It also has a
!=.Pattern matching is different.
Yeah, I just said it since you used it with null. I used it a lot for enums
The type matching is the most common thing I use it with. Combined with inline variables.
if (x is string { Length: 5} s) { // do stuff with s }And switch expressions.
As a side note inline variables are amazing haha
Stuff can be two things
ifnt instead of ifn’t
I’m just hoping this paves the way to code with Southern dialect
iffun is == true iffun ain't == falseMay I introduce you to the joys of #define and creating your own horrible sub language
That reminds me of an old paper about how to create a compilable C program out of old game ROMs. Decompile to assembly. Implement a bunch of
statements that implement all the ASM statements. Now compile it to a native binary on whatever platform.Won’t likely be faster or more accurate than regular emulation methods, but it’s a neat idea considering that the source code on all this stuff was lost a long time ago.
Ding ding ding ding ding ding…
