Re: [anjuta-devel] Rethinking the AnjutaProjectNode API

Hi Abderrahim,

Le 17/08/2011 12:19, Abderrahim Kitouni a écrit :
What do you think of the attached patch?

It's fine but I cannot apply it, I have an error in the .vapi file.

--- plugins/language-support-vala/libanjuta-3.0.vapi
+++ plugins/language-support-vala/libanjuta-3.0.vapi
@@ -429,11 +429,13 @@
public unowned GLib.List<Anjuta.ProjectProperty> get_custom_properties ();
                public unowned GLib.File get_file ();
                public Anjuta.ProjectNodeType get_full_type ();
+ public unowned Anjuta.ProjectNode get_group_from_file (GLib.File directory); public Anjuta.ProjectProperty get_map_property (Anjuta.ProjectProperty property, string name);

In the latest version of anjuta
                public Anjuta.ProjectProperty get_map_property
is not present.

There is perhaps other difference, so could you check again.

I think a string is better when you think about high level languages:
the address of a constant + pointer comparison is (Ok in C; hackish in
Vala; impossible in Python) while string comparison is (cumbersome in C;
Ok in Vala; Ok in Python).

I have expected a bit such answer :). We could have an enumerate value instead but I'm afraid it will be a bit annoying to allocate values.

I'll try to write a patch for this.


Best Regards,


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]