[Vala] GLib.IOFlags corrections

Without the patch using the flags won't compile. Hans diff --git a/vapi/glib-2.0.vapi b/vapi/glib-2.0.vapi index 3eaa980..2a31671 100644 --- a/vapi/glib-2.0.vapi +++ b/vapi/glib-2.0.vapi @@ -1553,9 +1553,9 @@ namespace GLib { public enum IOFlags { APPEND, NONBLOCK, - READABLE, -

Re: [Vala] Zeitgeist porting

First off, I think Vala is a good choice, but for a completely different reason than what has been said here. Mono is quite fast, and just because it has a runtime does not mean it can't be. Remember that mono does JIT your code into native assembly at startup (most tests i've made take between

Re: [Vala] Zeitgeist porting

On Sat, 4 Apr 2009 13:35:53 -0700 Christian Hergert christian.herg...@gmail.com wrote: First off, I think Vala is a good choice, but for a completely different reason than what has been said here. Mono is quite fast, and just because it has a runtime does not mean it can't be. Remember

[Vala] Idea: Change escaped comments to Logger calls

Usually a programmer writes comments about what the next few code lines will do. When something goes wrong, stdout.print() or Glib.debug() lines are also inserted for debug purposes: // Opening a file Glib.debug(Opening a file); ... code block ... It isnt a good thing document something twice,