Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Levi]

Spaceship operator comes up almost everytime I want to sort something in ruby.

obj_list.sort{|a,b|  b.hotness <=> a.hotness}

Or if I want to sort on multiple criteria, then I get to pair it with questionmark-colon:

obj_list.sort{|a,b|  (b.hotness != a.hotness ? b.hotness <=> a.hotness : b.snazziness <=> a.snazziness)}

[MagmaMcFry]

I'm particular to the binding operator ("=~"). Dunno if it exists anywhere but Perl, but what it does is apply a regular expression match or substitution to a string.

[da_nang]

So <=> is basically a comparator while my brain keeps thinking it should be equivalence. It's somewhere around the "Why doesn't this language support caret-exponentiation!?" level of pet peeve.

[alexandertnt]

Mine is the Goes To operator.

*runs away and hides*

[Putnam]

My favorite is COMEFROM

[Rose]

I'm going through the Android app dev tutorial on their site, and so far my feelings are summarized with this: "Android is weird."

All these "intents" and "fragments".. how do you even get a game working with this?

Make the game in Unity?

[GlyphGryph]

Second best operator is good old questionmark-colon.

The Ternary Operator.

Well, I mean, it's not literally the only ternary operator, but it's the only one you're likely to ever see, so it's still called "the" ternary operator.

[Putnam]

Lua does that funny; instead of undescribedVariable =  someCondition ? ifTrue : ifFalse, it's undescribedVariable =  someCondition and ifTrue or ifFalse.

[GlyphGryph]

That... would not result in the same behaviour.

if a= true
b= false
c= true

a ? b : c
=> false;
a and b or c
=> true

The Lua way equivalent is:
if a then b else c end

Or something thereabouts.

Personally, I would never use the method you described - it's a great way to shoot yourself in the foot and lead to laborious and difficult to figure out bugs later on.

I don't know the Lua rules for truthiness, those would determine how likely writing it that way is to screw you over. A glance at the internet shows that the only falsy values in Lua seem to be actual "false" values and "nil" values, so it would potentially be a rare problem... but that would make it all the more difficult to track down if it occurred.

[MorleyDev]

Imma let you finish but Scala has the best ternary operator

It's just

Code: [Select]

val y = true
val x = if (y) 10 else 20

Of with multiple ifs

Code: [Select]

val y = 30
val x = if (y == 20) "hello"
    else if (y == 30) "world"
    else "piano!"

Or pattern matching

Code: [Select]

val y : Option[Boolean] = Some(true)
val x = y match {
    case Some(true) => "Hello"
    case Some(false) => "World"
    case None => "Trinary!"
}

Turns out making everything have some return value actually is pretty cool. I actually have started to miss it when working in other languages.

All these "intents" and "fragments".. how do you even get a game working with this?

I think most of those are  for UI applications, so for "give me OpenGL canvas and draw to it" aren't particularly useful.

[MorleyDev]

So double post, but...

Am I the only person on this entire planet who managed to stumble across how you can launch a build for any compiler through cmake without invoking the actual build tool directly?
cmake --build [cache location]

It even has build in support for targets
cmake --build [cache location] --target install

And for configuration (which is vital for multi-config makefiles, like the solutions generator for Visual Studio).
cmake --build [cache location] --config debug
cmake --build [cache location] --config debug --target install

It just seems like nobody ever uses these, never recommends them on stackoverflow, nothing. Either I'm missing an obvious flaw, or it seems like nobody actually knows about this incredibly useful feature! 0_o

[Kirbypowered]

So I'd like to start some progress towards making my own roguelike in C++...Any suggestions on where to start? What I should know, learn about, where/how to learn it, and the like would be useful.

For reference, I'm currently able to put together simple little programs that function solely through the command prompt using preexisting libraries and the like. Most recently, I made a nifty little program to convert a number of any base into any other base (which ended up being simpler than I expected...), up to base 16. Really boosted my moral to be able to make it, but feel free to point and laugh at my lack of programming skills.

[MagmaMcFry]

1) Ask yourself "How much of a roguelike can I do right now?". Do that.
2) Ask yourself "What does my roguelike need next? Do I know how to code that?" If yes, code that. If no, make your idea simpler until you can code that, then code that.
3) Ask yourself "Is there a part of my program that I am able to expand and add features to?" If yes, do that.
4) Ask yourself "Is there any part of my program that could have been written better?". If yes, fix that.
5) Go to step 2.

[Kirbypowered]

Spoiler: Progress (click to show/hide)

am i doing it right

[Twiggie]

yup. what you gonna add next?