I don't know what your legal options would be if someone took code
that you went and showed them, versus code that they had to actively
discover through reverse engineering (however easy or difficult it
would be), but perhaps the former is easier to defend.
Your legal options are the exact same as for people who work in the
printed word business. You can't "compile" a book -- so by default
you get the "source code".
If someone violates your copyrights by copying some of your work into
their own books, you can take them to court and sue for damages (in
most countries, at least). Source code is no different.
True, though I don't have to agree to a license agreement to purchase
and read a book. I was thinking in this context the license agreement
which specifically forbids reverse-engineering would give you more
options than strictly dealing with copyright law. But IANAL.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
