Does you know who still cube anymore?

[tim]

Of course I am morally obligated to disapprove of his cheating, but the money is really the big issue, as it is of actual value (whereas "sentimental" value means crap, really)).

value_of(Human.new) = value_of(5000$) = 0.

 

[joey]

value_of(Human.new) = value_of(5000$) = 0.

SyntaxError: compile error
(irb):7: syntax error, unexpected '=', expecting $end
value_of(Human.new) = value_of(5000$) = 0
^
from (irb):7
from :0

 

[tim]

value_of(Human.new) = value_of(5000$) = 0.

SyntaxError: compile error
(irb):7: syntax error, unexpected '=', expecting $end
value_of(Human.new) = value_of(5000$) = 0
^
from (irb):7
from :0

It has to be your crappy compiler. The code works fine on my machine.

 

[Mike Hughey]

value_of(Human.new) = value_of(5000$) = 0.

SyntaxError: compile error
(irb):7: syntax error, unexpected '=', expecting $end
value_of(Human.new) = value_of(5000$) = 0
^
from (irb):7
from :0

It has to be your crappy compiler. The code works fine on my machine.

No, Tim; I think it's just that your compiler isn't properly written to spec. Must be a Microsoft compiler.

 

[Lt-UnReaL]

Why is everyone saying if he pays back the money? He stole money, obviously he has to pay it back or wouldn't something bad happen? Or was it some loophole in the WCA rules or what?

 

[Lucas Garron]

value_of(Human.new) = value_of(5000$) = 0.

SyntaxError: compile error
(irb):7: syntax error, unexpected '=', expecting $end
value_of(Human.new) = value_of(5000$) = 0
^
from (irb):7
from :0

It has to be your crappy compiler. The code works fine on my machine.

No, Tim; I think it's just that your compiler isn't properly written to spec. Must be a Microsoft compiler.

"value_of[Human.new] == value_of[5000 $] == 0"
doesn't evaluate in Mathematica. Must depend on context and definitions.

(Unless you meant =, not ==, which is just a definition...)

 

[tim]

class Object
  def value; 0; end
end

class Human
end

class Money
  def initialize(value)
    @value = value
  end
end

h = Human.new.value
m = Money.new(1000).value

p (h == m and m == 0)

=> true

 

[joey]

class Object;def value;0;end;def self.const_missing(name);eval("class #{name};
def initialize(v=nil);end;end");const_get(name);end;end
p (Human.new.value==(m=Money.new(1000).value)&&m==0)

=> true

 

[Dene]

So you're saying he can't come back before returning the money because he can't come back before returning the money? Now that was an empty answer.

Yes, it's always so easy to "bet" if you know what you "bet" about can't be tested. I believe he can't do it, otherwise he would've. Apparently full-solve cheating was the entire method so I have no idea what he's really capable of.

First statement: Well I think Erik gave a more thorough account of the situation now.

Second statement: Of course, what I "bet" (which has been taken way out of context, might I point out) can be tested, but only if he comes back. I'm certain that if he intends to come back, he will be working extremely hard to do things genuinely just to rub it in peoples faces (of course, his method would have to be a practical one, which would still prove him to have been lying before).