On Thu, Aug 13, 2009 at 1:20 PM, Ben Schulz <[email protected]> wrote:
>
> > So operator overloading is bad because people have HR problems?
>
> Why stop at operator overloading? To hell with all safe guards.. No
> more speed limits or safty belts; let's everyone just drive
> reasonably. And what's with architects and statics? It'll hold.
Safe guard?
This has nothing to do with safe-guards.
There's nothing about a method name that has _anything_ to do with it's
behavior.
def *(foo : Integer) = throw new RuntimeException("Haha, got you!")
def multiply(foo : Integer) = throw new RuntimeException("Haha, got you!")
Now, if you're in a situation where you're not doing any unit tests, you
work with less-than-stellar developers, it's not going to matter wether you
call * or multiply, it's going to suck anyways.
So the morale of the story is: If you have an HR problem, deal with it -
educate them, start unit testing, start to have code reviews etc.
>
>
> > Don't blame the gun, blame the shooter.
>
> Yes, because *that's* how you bring people back from the dead.
Why would you want to do that?
>
>
> With kind regards
> Ben
> >
>
--
Viktor Klang
Rogue Scala-head
Blog: klangism.blogspot.com
Twttr: viktorklang
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en
-~----------~----~----~----~------~----~------~--~---
