Print

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

[Orpheon]

You're gonna have to help me out with that one, because that genuinely makes no sense at all.

A variable on everything is one option. The other option is to make a general "Shot" class (f.ex.), and use some two separate "Shot_red" and "Shot_blue" classes that have separate code.
Both of them feature flexibility.

[Saniblues]

I don't really see the point in doing that when you could easily alter how they function by using the variable that assigns their team. And we would only need a boolean if we're using the shot_red and shot_blue argument here.

[NAGN]

it'd be good design to assign a .team variable to everything, and assign the numerical number to a constant.

It wouldn't make any sense to essentially hard code the two teams when behavior works identically

[Orpheon]

Alright. Then what I decided and already implemented was correct.

[Glock Topic]

team = True or False or None

 

[Saniblues]

team = True or False or None

 

put this man on the dev team

[Phantom Brave]

can bools really contain null
because if so then this guy is a genius

[Glock Topic]

can bools really contain null
because if so then this guy is a genius

bools are immutable

[Phantom Brave]

no sir that is not how data types work

[nightcracker]

no sir that is not how data types work

Yes sir, in Python bools, int's, None, str's among others are, in fact, immutable.

[Phantom Brave]

I don't want to live in a world where people refer to consts while talking about storing dynamic data
I really don't

[Glock Topic]

no sir that is not how data types work

Yes sir, in Python bools, int's, None, str's among others are, in fact, immutable.

and tuples

[nightcracker]

I don't want to live in a world where people refer to consts while talking about storing dynamic data
I really don't

Assuming you're talking to me, I was talking about immutable, not constant.

Variable in Python's are more "names" for objects than anything. When I say a = 1 I assign the name "a" to 1. When I say a += 1 I'm actually saying a = a + 1, meaning I assign the name "a" to the value of "a" with one added. The int object with value 1 never changed.

This is also the reason the ++ operator doesn't exist in Python.

[nightcracker]

no sir that is not how data types work

Yes sir, in Python bools, int's, None, str's among others are, in fact, immutable.

and tuples

As I said, among other things (frozenset)

[Orpheon]

I still prefer integer constants for team stuff because there isn't really a good reason why to use bools and it forces us to use signed bytes in syncing (something I don't like) or some extra if conditionals.

If we allow None, we can't do easy if checking, so we'll have this

Code: [Select]

if team:
...
elif team == False:
...
else:
...whilst with constants we would have

Code: [Select]

if team == constants.TEAM_RED:
...
elif team == constants.TEAM_BLUE:
...
else:
...
I prefer the latter. It's a lot more readable.