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 315986 - [API] GstStateChangeReturn enum members have same prefix as GstStateChange ones
[API] GstStateChangeReturn enum members have same prefix as GstStateChange ones
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.9.x
Other Linux
: Normal normal
: NONE
Assigned To: Andy Wingo
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-11 13:06 UTC by Thomas Vander Stichele
Modified: 2005-11-14 14:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Vander Stichele 2005-09-11 13:06:53 UTC 
see GST_STATE_CHANGE_SUCCESS vs GST_STATE_CHANGE_NULL_TO_READY
Comment 1 Tim-Philipp Müller 2005-09-17 18:37:16 UTC 
I think this was done on purpose to keep the enums short.
GST_STATE_CHANGE_RETURN_SUCCESS is way too long IMHO, same for
GST_STATE_TRANSITION_NULL_TO_READY.

Also, we have GstFlowReturn and GST_FLOW_OK etc., so at least there are other
cases where the prefix does not match the type. 

Is this awkward for language bindings or primarily an aesthetic issue?

</random comment>

Cheers
 -Tim
Comment 2 Andy Wingo 2005-10-21 12:26:32 UTC 
I think it's ok, doesn't bother guile or python either.
Comment 3 Andy Wingo 2005-11-14 14:22:00 UTC 
Closing as NOTABUG