Mono supports aot, which is compiling into native code. This is what they do for the iPhone, compile .net to native. The iPhone constraints include jitting, hence the need for compiling to native code.
Regards Sean Cross CIO Catalyst Risk Management PO Box 230 Napier 4140 DDI: 06-8340362 Mobile: 021270 3466 Visit us at http://www.catalystrisk.co.nz Offices in Auckland, Hamilton, Napier, Wellington, Christchurch & Dunedin Disclaimer: "The information contained in this document is confidential to the addressee(s) and may be legally privileged. Any view or opinions expressed are those of the author and may not be those of Catalyst Risk Management. No guarantee or representation is made that this communication is free of errors, viruses or interference. If you have received this e-mail message in error please delete it and notify me. Thank you." -----Original Message----- From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On Behalf Of Jolyon Smith Sent: Thursday, 17 September 2009 4:58 p.m. To: 'NZ Borland Developers Group - Delphi List' Subject: Re: [DUG] A change in upgrade policy coming from Embarcadero You can pre-compile any .NET code, even for Windows. I believe this is all that the C#-on-iPhone does, as well as eliminating (or ensuring that the code does not contain) any constructs that violate the iPhone constraints (no self-modifying/dynamically executed code for example). But if you mean can you compile a .NET application such that you create an entirely free-standing "native" Windows executable, the answer is no. You will always be dependent upon VBRUN.... oops I mean, "the .NET framework". ;) _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to delphi-requ...@delphi.org.nz with Subject: unsubscribe
