I have a little gtk+-2.0 project i wrote but when compiling it does complete
but I'm getting warning about the .h and .c files. Mostly type warnings.
Should I be concerned about this or submit a bug report? The function calls
match the signatures listed on the vala doc site.
Matt
_
Those defines should be defined by vala internally? All systems can be
identified by __linux__ __FreeBSD__ ... do you think this should be defined by
vala? Autoconf is imho not the right place for this.
On 23/03/2011, at 12:41, Marco Trevisan (Treviño) wrote:
> Il giorno mer, 16/03/2011 alle 1
sorry if I break threading on this post.
I am replying to this mail:
http://mail.gnome.org/archives/vala-list/2011-March/msg00134.html
I lost the original posting.
I posted a gtk+ 3.0 example in February:
http://mail.gnome.org/archives/vala-list/201
Hello,
في ر، 23-03-2011 عند 20:20 +0900 ، كتب san hoi:
> vala : 0.10.7
> os : fedora 15
>
> I try to compile customwidget sample in gtk+-3.0. (
> http://live.gnome.org/Vala/CustomWidgetSamples#Subclassing_Gtk.Widget
> )
> but it cannot work.
[...]
>
> Is there vala's tut
في ث، 22-03-2011 عند 19:17 +0100 ، كتب Pavol Klačanský:
> Hi, why this not works? I looked at shotwell code, and it is written
> same way in it
It would be easier to help you if you can post a simple and
self-contained example that's not working. With just an error message,
one cannot understand yo
On Thu, Mar 24, 2011 at 11:01:24AM +0900, san hoi wrote:
> Sorry for sending next one more question to list.
> I try to receive error message which vala's compiler output.
>
> >>> f=file("data.out", "w")
> >>> cmd = "valac -v hello.vala"
> >>> p=subprocess.Popen(cmd, shell=True, stdout=f, stderr=
Sorry for sending next one more question to list.
I try to receive error message which vala's compiler output.
>>> f=file("data.out", "w")
>>> cmd = "valac -v hello.vala"
>>> p=subprocess.Popen(cmd, shell=True, stdout=f, stderr=subprocess.PIPE)
>>> errcode=p.wait()
>>> f.close()
>>> for line in f
Jim Peters wrote:
> Java has partial support for immutable GC'd objects by marking all
> public variables in the class as 'final'. So long as all the
> referenced objects are also immutable objects, then everything works
> out. The objects can be freely passed around without fear that some
> call