Jean-Philippe Barrette-LaPierre wrote:
I looked into libs/sound library. I think I'll use it into SFLPhone, but
something bothers me. I see that you use a Utility class as a list. I don't
have any problems to use that kind of utility classes within an application,
because I admit that STL is not always simple to use. The problem here is
that I'm not sure that this utility classes should be exposed within
libs/sound.
I think everyone has a different way of perceiving what should be a simple way
of using lists, but everyone knows how to use std::list. I think that a
library should always expose the STL. It means that you can use a utility
class, but expose only the STL. After that, if a user wants to use a
convenient class, he could use one. But I think users will always use a
different utility class than you. So, instead of exposing your utility class,
you should expose the STL one.
Within OpenWengo it means that if we want to use the STL for libs/audio, we
just need to add a constructor with a std::list as an argument. Then, you
wouldn't need to change any code within openwengo, and the library wouldn't
be dependant of your utility class.
What do you think?
Very sound idea, IMO
Vadim
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
