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 783434 - adaptivedemux: modify return value in each function
adaptivedemux: modify return value in each function
Status: RESOLVED WONTFIX
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-06-05 14:44 UTC by Jimmy Ohn
Modified: 2018-05-21 17:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
adaptivedemux: modify return value in each function (5.10 KB, patch)
2017-06-05 14:46 UTC, Jimmy Ohn
reviewed Details | Review

Description Jimmy Ohn 2017-06-05 14:44:50 UTC
modify some return value like another demux style such as qtdemux
Comment 1 Jimmy Ohn 2017-06-05 14:46:07 UTC
Created attachment 353189 [details] [review]
adaptivedemux: modify return value in each function

modify some return value like another demux style such as qtdemux.
Comment 2 Sebastian Dröge (slomo) 2017-06-06 06:36:59 UTC
Comment on attachment 353189 [details] [review]
adaptivedemux: modify return value in each function

Thanks for the patch, but why do you think this is an improvement?
Comment 3 Jimmy Ohn 2017-06-06 17:23:07 UTC
(In reply to Sebastian Dröge (slomo) from comment #2)
> Comment on attachment 353189 [details] [review] [review]
> adaptivedemux: modify return value in each function
> 
> Thanks for the patch, but why do you think this is an improvement?

we already declare ret variable above line. but it's not used in the each case even though we can use it. I think that it's better to analyze modified source code. Also, I refer to another demux code such qtdemux, avidemux.
Comment 4 Tim-Philipp Müller 2018-05-21 17:52:24 UTC
Thanks for the patch, but I think we should leave the code as it is, sorry!

It's not worth trying to make all code in GStreamer consistent in this respect, and I think where we can return TRUE/FALSE directly it makes sense to do so - it's much easier to follow the code and see what's happening in those cases.