Hi, I googled "Mono on WinCE" and found roughly nothing.
I've done some benchmarks and found that the .NET Compact Framework
3.5 has terrible performance, 3x to 11x slower than native (VC++)
code. In contrast, I found that "real" .NET (x86) has performance
similar to VC++, and Mono is between 50-1
ike a weird approach, since (the instructions imply) you have to install the mono binaries before you can build it anyway!
On 9/28/06, Raja R Harinath <[EMAIL PROTECTED]> wrote:
Hi,"David Piepgrass" <[EMAIL PROTECTED]> writes:> You're right, WinRAR screwed up the untarbal
reia Gaita <
[EMAIL PROTECTED]> wrote:On 9/28/06, David Piepgrass <
[EMAIL PROTECTED]> wrote:> By the way, the build instructions say to use ./configure> --prefix=/tmp/install and "feel free to use any prefix you want". What is> the prefix for? It seems to work without one
rsive] Error 1make[1]: Leaving directory `/cygdrive/d/Dev/University/ENCM599/mono-1.1.17.1'make: *** [all] Error 2On 9/26/06,
Andreia Gaita <[EMAIL PROTECTED]> wrote:
On 9/26/06, David Piepgrass <[EMAIL PROTECTED]> wrote:> - Why doesn't mono-1.1.17.1.tar.gz contain a gmcs direct
As a school project, I have decided to add unit checking to C# using annotations in comments. With this feature, you would potentially be able to write code like this...double average(IList list)
{ double total = 0; for (int i = 0; i < list.Count; i++) total += list[i]; return tota
