Re: [Live-devel] Tracked down the problem with latency

2013-03-11 Thread Ross Finlayson
On Mar 11, 2013, at 12:01 PM, Chris Van Brederode wrote: > We're in somewhat of a time crunch here Do "we" not have our own domain name? :-) Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live

Re: [Live-devel] Tracked down the problem with latency

2013-03-11 Thread Chris Van Brederode
Thanks for the reply I went ahead and re-implemented MPEG4VideoFileServerMediaSubsession (as MPEG4VideoFileServerMediaSubsession2) using a preferredFrameSize of 200. I did this before you responded, and it turned out it works relatively well. VLC still has some hiccoughs here and there with the

Re: [Live-devel] Breaking change

2013-03-11 Thread Jeff Shanab
The namespace would allow us to get away from the define which is a text substitution and is what causes the clash. However. What about something like #if Defined(USE_LIVE555_NAMESPACES) # define OPENLIVENS namespace { # define CLOSELIVENS } // close namespace LIVE555 # define LIVENS LIVE555

Re: [Live-devel] Breaking change

2013-03-11 Thread Nikolai Vorontsov
Hi Chris, have you ever seen C++ compiler for embedded systems? They are far away from full c++ 2003 compliance (mostly as not so many C++ features are used in embedded development - RTTI, exceptions, namespaces, templates - just a few samples). Nikolai From:

Re: [Live-devel] Breaking change

2013-03-11 Thread Chris Van Brederode
On Mon, Mar 11, 2013 at 11:02 AM, Nikolai Vorontsov < nikolai.voront...@quadrox.be> wrote: <--snip--> ** > Also, if some of supported compilers doesn't use namespaces (well, may be > some embedded one) - then you might need to use conditional compilation as > you did over 9000 times before ;-) >

Re: [Live-devel] Breaking change

2013-03-11 Thread Ross Finlayson
> may be the easiest solution for such issue is to wrap all Live555 > functionality in a namespace? And place "using namespace Live555;" somewhere > in it's header. Yes, that's certainly a possibility for the future. To date, however, I've avoided using C++ namespaces, because I don't want to

Re: [Live-devel] Breaking change

2013-03-11 Thread Nikolai Vorontsov
Hi Ross & Jeff, first of all in Boost 1.49 I didn't find a Boolean class. May be it's in a newer version defined. Second, Ross - the issue here is that someone might need to have to include both Live555 and other library (boost or libvc) headers to his _single_ source file. If other library de

Re: [Live-devel] Breaking change

2013-03-11 Thread Nikolai Vorontsov
Hi Ross, may be the easiest solution for such issue is to wrap all Live555 functionality in a namespace? And place "using namespace Live555;" somewhere in it's header. Then people that uses boost (or any other library that clashes with your lib by internal names/types) should not have a problem.

Re: [Live-devel] Breaking change

2013-03-11 Thread Ross Finlayson
> I am updating live555 from 2012.2.29 to 2013.03.07 and found a change in > Boolean.hh that breaks my build. From reading the changelog, I think this is > recent. > > The line > “ #define Boolean bool “ No, it's *not* recent; it's almost 9 months old! From the changelog: 2012.06.12: - U

[Live-devel] Breaking change

2013-03-11 Thread Jeff Shanab
I am updating live555 from 2012.2.29 to 2013.03.07 and found a change in Boolean.hh that breaks my build. From reading the changelog, I think this is recent. The line " #define Boolean bool " Overwrites a class name in boost (move.cpp) where there is a class with the name Boolean In th