0 Members and 1 Guest are viewing this topic.
smithy wrote:QuoteSamuraiCrow wrote:@smithyThere is a licence fee that must be paid for distribution of the Java Classes. That's why AmigaDE didn't ship with them by default but, instead, required you to download them from Sun's site.Ahhhh.. I didn't know that... but hopefully this will be covered in the open source terms - otherwise it won't really be open source!
SamuraiCrow wrote:@smithyThere is a licence fee that must be paid for distribution of the Java Classes. That's why AmigaDE didn't ship with them by default but, instead, required you to download them from Sun's site.
smithy wrote:You are talking about the difference between using a JIT JVM and a non-JIT JVM. But this has nothing to do at all with GCJ because GCJ is just a compiler - it compiles Java source code into bytecode. It doesn't attempt to run it, so no JIT is involved or needed.You can run bytecode created by GCJ on any compliant JVM, JIT or not. There is no need to recompile it based on whether you use a JIT JVM.So static or dynamic compilation doesn't really apply here, because one, or both can be done, it's up to you.My original question was, how does Sun's decision to open up it's JVM impact GCJ, a source-compiler?