|
Authored by: Ed L. on Friday, May 04 2012 @ 06:16 PM EDT |
Would those be human tools, or software? Assuming the latter, the obvious
question is "Just how 'Java-like' is your tool?" Because as someone on another
thread observed, a finding of API/SSO copyright-ability could have some curious
consequence. Consider
XobotOS,
f'rinstance:
XobotOS project
===============
XobotOS is a Xamarin
research project that explored porting Android 4.0 from Java/Dalvik to C# to
explore the performance and memory footprint benefits of C#.
XobotOS is a
semi-automated port of the Android 4.0 source code fromJava to C#. The
automated parts were ported using an improved version of Sharpen that can
compile more advanced Java constructs and supports
generics. Most of the manual
bits of code fall in two categories (a)
code to integrate with the host
operating system and (b) replace the
Java JNI code used to call into C, with the
ECMA CLI P/Invoke
functionality.
So one appears to have a machine
translation of Harmony/Android to
C#/.NET. Does that make the latter's
interface a "derived work" of the former? Of Java as well? What is "fair use?"
Where does it end?
--- Real Programmers mangle their own memory. [ Reply to This | Parent | # ]
|
|
|
|
|