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 627890 - [GScanner] the token field should be declared as guint and not as GTokenType
[GScanner] the token field should be declared as guint and not as GTokenType
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: general
2.25.x
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-08-24 20:48 UTC by Javier Jardón (IRC: jjardon)
Modified: 2018-05-24 12:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Javier Jardón (IRC: jjardon) 2010-08-24 20:48:52 UTC 
Because of this I get warnings when compiling GTK+ like this:

gtkbindings.c: In function 'gtk_binding_parse_signal':
gtkbindings.c:1443:2: warning: case value '45' not in enumerated type 'GTokenType'
gtkbindings.c: In function 'gtk_binding_parse_bind':
gtkbindings.c:1508:22: warning: comparison between 'GTokenType' and 'enum <anonymous>'
gtkbindings.c:1509:22: warning: comparison between 'GTokenType' and 'enum <anonymous>'
gtkbindings.c:1511:27: warning: comparison between 'GTokenType' and 'enum <anonymous>'
Comment 1 Emmanuele Bassi (:ebassi) 2010-08-24 21:15:12 UTC 
the correct way to handle this is to fix GScanner to declare the @token member; the other option is to cast scanner->token to guint before checking it; in this case, this code:

  switch (scanner->token)
    {
    ...

should become:

  guint token = (guint) scanner->token;
  switch (token)
    {
    ...
Comment 2 Javier Jardón (IRC: jjardon) 2010-08-25 16:17:03 UTC 
Filled bug #627962 to fix GTK+ warnings
Comment 3 GNOME Infrastructure Team 2018-05-24 12:41:50 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/336.