Re: [Vala] use weak and var together

2009-01-11 Thread Jürg Billeter
On Sat, 2009-01-10 at 23:48 +0100, Hans Vercammen wrote: Why do this manually? Don't you need to chain the dispose handlers throughout the hierarchy to make it usable somehow? As far as I understand the GObject dispose mechanism, it doesn't prevent the cyclic references from not being cleaned

Re: [Vala] Header file generation

2009-01-11 Thread Arto Karppinen
Jürg Billeter wrote: I want to finally solve issues we're having related to generation of C header files. The current situation is that valac generates a .h file in addition to a .c file for each .vala source file. The .h files describe both, the public and the internal, C API. There are

Re: [Vala] Header file generation

2009-01-11 Thread Vlad Grecescu
On Sun, Jan 11, 2009 at 3:14 PM, Jürg Billeter j...@bitron.ch wrote: * Generate two sets of header files For each source file foo.vala, we could generate foo-priv.h in addition to foo.c and foo.h and move the internal C API there. One issue with this approach is that it clutters the

Re: [Vala] Header file generation

2009-01-11 Thread Jürg Billeter
On Sun, 2009-01-11 at 16:41 +0200, Arto Karppinen wrote: Jürg Billeter wrote: * Header file interdependencies Header files often depend on other header files and sometimes these dependencies form cycles. These cycles are currently detected by the compiler and resolved as far as

Re: [Vala] subclassing a template class

2009-01-11 Thread Yu Feng
On Sun, 2009-01-11 at 14:50 +0100, Jürg Billeter wrote: On Sat, 2009-01-10 at 19:32 -0500, Yu Feng wrote: I made a patch to accept the following syntax: class ContainerT { ... } class Stuff: ContainerWidget { Stuff() { baseWidget(); } } Bug #567319

Re: [Vala] exposing the unref and ref member for gtypeinstance classes?

2009-01-11 Thread Yu Feng
On Sun, 2009-01-11 at 15:07 +0100, Jürg Billeter wrote: Hi Yu, On Sat, 2009-01-10 at 13:11 -0500, Yu Feng wrote: Is it possible to expose ref and unref member of gtypeinstance classes? They will be useful with GHashTable.new_full I am currently using a dirty workaround like this:

Re: [Vala] [ANNOUNCE] Vala 0.5.5 - Compiler for the GObject type system

2009-01-11 Thread Nicolas Joseph
The win32 installer: http://code.google.com/p/valide/downloads/detail?name=vala-0.5.5.exe 2009/1/10 Jürg Billeter j...@bitron.ch We are pleased to announce version 0.5.5 of Vala, a compiler for the GObject type system. Vala 0.5.5 is now available for download at:

Re: [Vala] Header file generation

2009-01-11 Thread Yu Feng
My point on this. I took a look at gtkwidget.c and gtkcontainer.c. GtkWidget has a parent reference to GtkContainer so it should have circular header files. It turns out they avoid the cycle by defining the parent member of GtkWidget as a GtkWidget instead of what it should be (GtkContaienr).

[Vala] HashTableQuark, void* broken in trunk.

2009-01-11 Thread Yu Feng
Dear Jurg, HashTableQuark, void* is broken in trunk with an error: error: `GLib.Quark' is not a supported generic type argument, use `?' to box value types But Quark is actually a SimpleType. Is SimpleType no longer propagated? Yu ___ Vala-list

[Vala] volatile variables?

2009-01-11 Thread Yu Feng
Hi all, How do I declare a volatile double variable? Yu ___ Vala-list mailing list Vala-list@gnome.org http://mail.gnome.org/mailman/listinfo/vala-list

Re: [Vala] volatile variables?

2009-01-11 Thread Christian Hergert
Is that even be possible on 32bit? sizeof(gdouble) is 8. -- Christian On Sun, 2009-01-11 at 17:54 -0500, Yu Feng wrote: Hi all, How do I declare a volatile double variable? Yu ___ Vala-list mailing list Vala-list@gnome.org

Re: [Vala] volatile variables?

2009-01-11 Thread Yu Feng
hmm. I thought if I declare something as volatile they will be stored in memory instead of registers. On i386 FPU the double numbers in the register has a higher precision than the double numbers in memory and the compilier optimization is apparently causing me troubles: by adding a stdout.print

Re: [Vala] Header file generation

2009-01-11 Thread Hans Vercammen
On Sun, 2009-01-11 at 14:14 +0100, Jürg Billeter wrote: * Internal API The whole point of an internal API is that it is internal, and we should therefore aim to separate public from internal header files. Yes, that sounds like a very good idea. Could we extend this with G_GNUC_INTERNAL