After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 583598 - Vala and class variable in interfaces
Vala and class variable in interfaces
Status: RESOLVED DUPLICATE of bug 546440
Product: vala
Classification: Core
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-22 22:17 UTC by Maciej (Matthew) Piechotka
Modified: 2011-08-08 20:42 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Fix error message for Bug 583598 - Vala and class variable (1.47 KB, patch)
2011-07-26 07:32 UTC, geert jordaens 		none Details | Review

Description Maciej (Matthew) Piechotka 2009-05-22 22:17:15 UTC 
Please describe the problem:
Wrongly reported error (in case which should be feature anyway)

Steps to reproduce:
interface Test : GLib.Object
{
    class int i;
}


Actual results:
warning: field `Test.i' never used
error: class fields are not supported in compact classes


Expected results:
warning: field `Test.i' never used
error: class fields are not supported in interfaces

or (preferably):

warning: field `Test.i' never used



Does this happen every time?


Other information:
Comment 1 Michael 'Mickey' Lauer 2009-10-14 22:51:03 UTC 
Confirming, the error message should be fixed.
Comment 2 geert jordaens 2011-07-26 07:32:06 UTC 
Created attachment 192647 [details] [review]
Fix error message for Bug 583598 - Vala and class variable
Comment 3 Luca Bruno 2011-07-26 13:21:54 UTC 
Class fields could be ideally supported for interfaces.
Comment 4 geert jordaens 2011-07-31 11:36:48 UTC 
With the restriction that they have to be static. This sounds like another bug report (enhancement). This is about the current error message.
Comment 5 Luca Bruno 2011-08-08 20:42:24 UTC 

*** This bug has been marked as a duplicate of bug 546440 ***