Thread history

A few thoughts:

• IANAL...
• I don't think it means Nene is under RWPCL, only that perhaps it should be, and that you are risking a lawsuit from Jamougha by breaking the license. =)
• I'm almost certain you can rewrite the RWPCL parts and then be free of the viral licensing obligations.
• Code can definitely exist under multiple, totally different licenses.
• If Rednaxela already released his kd-tree under zlib, then someone releases a bot with his kd-tree and Raiko's RWPCL gun, it couldn't possibly retroactively make his kd-tree RWPCL.
• Some code would never hold up to scrutiny in terms of copyright infringement - I wouldn't worry about things like absoluteBearing, project, and lots of other trivial stuff. I've read that you probably couldn't copyright a tweet, and these are far less content than that.

(Edit: Oops, guess I'm late, but anyway...)

I use angleToEnemy rather then absoluteBearing. I have for awhile. Since absoluteBearing was generally semi-meaningless to me... (absoluteBearing to what?)

Though I could easily see an argument otherwise. Robocodes api confuses the matter with getBearing(). Since otherwise bearing could mean 'the angular direction of a line, point, or course measured from true north or south', where in this case, it is actually the angle 'the amount of rotation needed to bring one line or plane into coincidence with another'.

Absolute bearing is relative to the angle pointing up (north), relative to the battlefield. Making it independent from bots headings. Just guessing, didn´t look at the code.

Basically, I was just saying that getBearing is poorly named, and I don't use absoluteBearing since it doesn't make any sense to me. Since 'bearing' by itself is by definition an angle relative to some fixed direction (which getBearing confuses the meaning of, returning data from a different frame of reference to all other methods).

I guess those licenses are enforced by honor code only. With no law involved.