[gobject-introspection] __extension__ can be put in front of expressions



commit b20b019737118778666b1b9b75ea5d33b7880d58
Author: Damien Lespiau <damien lespiau intel com>
Date:   Sat Dec 26 15:32:20 2009 +0100

    __extension__ can be put in front of expressions
    
    glib uses __extension__ in macros dealing with 64 bits integer such as
    GUINT64_SWAP_LE_BE().
    
    To quote the GCC manual:
      `-pedantic' and other options cause warnings for many GNU C extensions.  You
      can prevent such warnings within one expression by writing `__extension__'
      before the expression.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=605779

 giscanner/scannerparser.y |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)
---
diff --git a/giscanner/scannerparser.y b/giscanner/scannerparser.y
index 7b18f94..b38fb89 100644
--- a/giscanner/scannerparser.y
+++ b/giscanner/scannerparser.y
@@ -534,6 +534,7 @@ assignment_operator
 expression
 	: assignment_expression
 	| expression ',' assignment_expression
+	| EXTENSION expression
 	  {
 		$$ = gi_source_symbol_new (CSYMBOL_TYPE_INVALID);
 	  }



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