From: Arno P. <ar...@pu...> - 2010-05-23 08:21:31
|
as a matter of fact, we will soon add an optimizing post-processor to XMLVM. Of course, its intention is purely for optimizing purposes, but as a nice side effect, it will be *a lot* more difficult to detect that the application was created by XMLVM. Now as Tor pointed out, what men can do, men can undo (of course the same is true for women). The question is, how much effort will Apple put into detecting such usages. My belief is: none at all! With the fear, uncertainty, and doubt they have been spreading with section 3.3.1, Apple effectively killed commercial products such as Adobe's CS5 or Novell's MonoTouch. XMLVM however is an open source project and it is your choice whether you use it or not. Arno On 5/23/10 9:34 AM, Ilya Lyashevsky wrote: > sounds like there might be another worthy project here -- cleaning up > tool-generated code to make it look man-made so as to avoid detection by > over-reaching, hyper-controlling corporations. > > On Sat, May 22, 2010 at 6:38 PM, Tor Lillqvist <tm...@ik... > <mailto:tm...@ik...>> wrote: > > > whether it is actually possible for apple to determine if the code > > of a submitted app was created using XMLVM or any other tool that > outputs > > native code. > > Of course it is. To an expert, it shouldn't be hard to recognize > patterns in the object code produced from source code generated by > XMLVM. (Or other similar tools.) After all, if you look at the > Objective-C output by XMLVM, it is easy to recognize. It doesn't look > like something a human would write, does it? Sure, an optimising > compiler will hide some of that, but still, I would be surprised if it > wasn't still recognizable on the object code level. > > --tml > > > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |