Quote:
- if you really do want to test that the pixels are getting drawn correctly, here are a few
Yeah that's not what I want to test eventhough it kind of sounds like that in my post. Agreed that that would basically be "testing the framework". What I want to test is that certain stuff gets drawn (existance) not that it's drawn correctly.
I.e. I have a level and want to test that player, enemy etc. are drawn/exist...I think I'll just write a test for draw that simply does player.draw and whatnot
Thx for being my rubber ducky
Also it's moot since it seems Rubygame is better for what I want to do than Gosu anyways (especially since I've worked with PyGame before). Gosu seems fairly limited feature wise
Quote:
Definitely the best solution.
Variable names need to be better. I'd rename salary to base_salary or something and total_comp would become slalary (compensation etc. are also fine but total_comp...what's that total_computation...total_computers_in_stock). I think salary = base_salary+bonus makes the most sense semantically.
Quote:
Your logic means you believe people should only ever declare immutable variables. It's not practical or reasonable.
If it's not practical or reasonable, can it at least be *cough* functional?
Also all this salary code reminds me of a funny quote from a programmer I interviewed who wasn't supergood at ze English (we hired him)...interview went something like this
"I see you worked on a couple of OS projects, that's nice"
"So uh why do you want to work here?"
Answer
Last edited by clowntable; 03-24-2012 at 07:55 AM.