This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: xlc 6 does not like bufferobject.c line22
Type: Stage:
Components: None Versions: Python 2.5
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: pruebauno, sjoerd
Priority: normal Keywords:

Created on 2006-09-13 15:32 by pruebauno, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg29811 - (view) Author: prueba uno (pruebauno) Date: 2006-09-13 15:32
The VisualAge 6 Compiler on AIX complains about the
extra comma on line 22 of bufferobject. Doing the
following change keeps the compiler happy.

enum buffer_t {
    READ_BUFFER,
    WRITE_BUFFER,
    CHAR_BUFFER,
-    ANY_BUFFER,
};

enum buffer_t {
    READ_BUFFER,
    WRITE_BUFFER,
    CHAR_BUFFER,
+    ANY_BUFFER
};
msg29812 - (view) Author: Sjoerd Mullender (sjoerd) * (Python committer) Date: 2006-09-13 15:49
Logged In: YES 
user_id=43607

That's a bug in the compiler, not in Python.  The C standard
has:

enum-specifier:
      enum identifieropt { enumerator-list }
      enum identifieropt { enumerator-list , }
      enum identifier
enumerator-list:
      enumerator
      enumerator-list , enumerator
enumerator:
      enumeration-constant
      enumeration-constant = constant-expression

From the first production you can see that the comma at the
end is allowed.  This has been true since at least 1980.
msg29813 - (view) Author: prueba uno (pruebauno) Date: 2006-09-14 13:22
Logged In: YES 
user_id=30777

All right, I guess I have to complain to IBM then :-)
History
Date User Action Args
2022-04-11 14:56:20adminsetgithub: 43970
2006-09-13 15:32:56pruebaunocreate