Linked by Thom Holwerda on Wed 2nd Aug 2006 06:37 UTC
After all the debate, gtk# will most likely find its way into GNOME. "The release team has completed its second meeting to try to finish the new module decisions. And, after all the long threads on d-d-l and the many discussions amongst ourselves trying to determine community consensus, we finally have the decisions. In summary: orca, alacarte, and gnome-power-manager are in; gtk# and tomboy are in, assuming the issues mentioned are resolved; sticky notes becomes deprecated, assuming tomboy issues are resolved and gets in." Update: Elijah Newren emailed me concerning an important aspect of the current decision, and asked me to highlight it. So, read more!
Permalink for comment 148506
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-29
I don't understand how mono applications are supposed to get advantage of AMD64, with more registers and new opcodes.
Mono applications can take advantage of AMD64 by running under a JIT which makes use of AMD64 registers & opcodes.
In short, upgrade the JIT (the mono program and libmono.so) so that it targets AMD64 instead of x86.
As this has already been done, all Mono applications can already take advantage of AMD64 registers & opcodes...
...With one exception: dependencies. Any non-trivial C# application will eventually rely on [DllImport] statements which invoke native libraries. (For example, Gtk# is basically a bunch of [DllImport]'s for the GTK+ libraries.) In order for a AMD64 mono to work, all of the dependencies your application uses must also be compiled for AMD64.
Since that has already been (largely) done, it should be possible to make full use of your AMD64 processor with mono now.