[vlc-devel] HLS player

Kevin Cadieux kcadieux at gmail.com
Mon Jun 17 01:57:28 CEST 2013

On Sun, May 19, 2013 at 6:08 AM, Jean-Baptiste Kempf <jb at videolan.org>wrote:

> To be honest, the question is more: "will you maintain this module
> correctly for a correctly long time?" than "what language is it in?"
> By experience, maintaing C code is easier than C++ modules, because more
> people are familliar with C code and because C++ programers often feel
> compelled to use "cool features" of the language, because they can.

> That being said, C++ makes sense when you need inheritance, like for MKV
> or MXF, or like for Dash, where you have multiple profiles.
> For HLS? why not, but:
>  - Do your first commits with the old code and transition. A rewrite from
>    scratch is not going to be accepted;
>  - Do not use templates or operator overload just because you can;
>  - Do not make it depend on 3rd party libs without asking (and no, Boost
>    is NOT ok);
>  - Do not reimplement stuff that should be in the VLC core;
>  - Prepare the transition to a Demux or an Access Demux module.

What do you mean exactly by "Prepare the transition to a Demux or an Access
Demux module"? So far the HLS module doesn't seem to be doing any demuxing
at all. Are you saying it should take on new responsibilities?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20130616/61951495/attachment.html>

More information about the vlc-devel mailing list