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 670022 - Names of const global variables (i.e. generated macroses for them) interfere with async closure members
Names of const global variables (i.e. generated macroses for them) interfere ...
Status: RESOLVED DUPLICATE of bug 790239
Product: vala
Classification: Core
Component: Code Generator
0.15.x
Other Linux
: Normal major
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-13 23:05 UTC by aleck.agakhan
Modified: 2018-02-21 13:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
const-interference-bug.zip (3.19 KB, application/zip)
2012-02-13 23:07 UTC, aleck.agakhan
Details

Description aleck.agakhan 2012-02-13 23:05:09 UTC
Names of const global variables (i.e. generated macroses for them) interfere with function params and async closure members

See attached files
if I declare global string variable like this:
    const string some_str = "hello world";
vala generates preprocessor macros:
    #define some_str "hello world"
(see line 30 in main.c)
which interferes with generated param in
    void method_async (const gchar* some_str, GAsyncReadyCallback _callback_, gpointer _user_data_) {
(see line 57 in main.c)
and closure members
    _data_->some_str
(see lines 52, 66, 86 in main.c)
Comment 1 aleck.agakhan 2012-02-13 23:07:38 UTC
Created attachment 207503 [details]
const-interference-bug.zip
Comment 2 Michael 'Mickey' Lauer 2018-02-21 13:23:57 UTC

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