Re: [Vala] Compile error (interfacing DBus)
Hi Hannes, On Tue, 2008-05-20 at 11:45 +0200, Hannes Matuschek wrote: I've tried to deal with HAL's DBus-interface but got some compile errors (compiling the C code). [...] Fails to compile: valac --pkg=dbus-glib-1 -o test src/main.vala main.c: In function 'us_backup_main': main.c:47: error: 'result' undeclared (first use in this function) main.c:47: error: (Each undeclared identifier is reported only once main.c:47: error: for each function it appears in.) error: cc exited with status 256 Compilation failed: 1 error(s), 0 warning(s) This was bug 529351. I've just committed a fix, it should work fine now with string[]. Jürg -- Jürg Billeter [EMAIL PROTECTED] ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] : benchmarks gobject
Hi, I have made this benchmarks only to demonstrate the performance of Vala versus C# (C++ has been added after the creation). In the case of C++, Vala may be better or worse depending the bench, like in plain-C [http://shootout.alioth.debian.org/gp4/c.php]. When you use many OO features of Vala, you loose the speed of plain-C and you only benchmarks the GObject sub-system ;). But I think that the runtime is really optimize and, has you can see in the binaryTrees benchmark, doesn't add runtime extra time. Regards 2008/5/20 Martin (OpenGeoMap) [EMAIL PROTECTED]: Hi: http://code.google.com/p/vala-benchmarks/wiki/BenchResults I always have a question about gobject. How is it posible than Gobject can be more quick than C++?? It´s supposed than in the compiling proccess c++ have the job done and gobject need runtime calculus. In big project like a CAD for example can be gobject succesful? Regards. ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
[Vala] gdk/gdkkeysyms.h excluded from gdk package
Hello, I need one of the following macros defined in the file gdk/gdkkeysyms.h. Like GDK_Up, GDK_Down, ... But I see the file is excluded from the gdk package. Why is it not included? and how can I access the GDK_Up macro? Thanks, Thijs ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
Re: [Vala] [PATCH] GIO nullable parameters
In fact I think I'll use such annotation on a samba4 module I'm working on, so if anyone wants to influence inline C representations of vala attributes, now is the time to do it. Sam -Original Message- From: Sam Liddicott [EMAIL PROTECTED] Sent: 20 May 2008 16:12 Cc: vala-list@gnome.org Subject: Re: [Vala] [PATCH] GIO nullable parameters * Frederik wrote, On 20/05/08 14:01: Jürg Billeter wrote: On Tue, 2008-05-13 at 12:09 +0200, Frederik wrote: I think in the GIO vapi bindings there are more parameters that should be marked as nullable. For example: etag as in File.replace() or progress_callback as in File.move(). Yes, we certainly still miss a lot of nullable annotations. I've been looking at the GIO documentation and spotted all nullable parameters. I have attached a patch for gio-2.0.metadata inclusive the newly generated vapi. This should cover all nullable parameters in GIO. I think it may be simpler to allow the null-able clue to be part of the C source using a macro indicator which can be compiled away in C. #ifndef VALA #define NULL_OK #endif ... send_to_mainloop_async (GLib.SourceFunc func, NULL_OK GLib.DestroyNotify notify); ... It enrichens the C source and allows the C maintainer to keep the hint alive effortlessly, rather than someone have to keep a meta file in sync. Sam ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list
