On Sun, Jun 8, 2014 at 10:03 AM, George Joseph
george.jos...@fairview5.com wrote:
Right now, the non-ref debugging code in astobj2 is triggered by a mix of
AST_DEVMODE and AO2_DEBUG and both get set if you want to run the test
framework. I've noticed though that the inclusion of the debugging
One thing I dislike about AST_DEVMODE is that changing it requires
rerunning ./configure. I feel ./configure should be restricted as much as
possible to checking dependencies. Any build configuration that is not
directly enabled/disabled by an external dependency should be in menuselect.
If we
On Mon, Jun 9, 2014 at 11:22 AM, Corey Farrell g...@cfware.com wrote:
One thing I dislike about AST_DEVMODE is that changing it requires
rerunning ./configure. I feel ./configure should be restricted as much as
possible to checking dependencies. Any build configuration that is not
directly
On Mon, Jun 9, 2014 at 5:45 PM, Richard Mudgett rmudg...@digium.com wrote:
On Mon, Jun 9, 2014 at 12:31 PM, George Joseph
george.jos...@fairview5.com wrote:
On Mon, Jun 9, 2014 at 11:22 AM, Corey Farrell g...@cfware.com wrote:
One thing I dislike about AST_DEVMODE is that changing it
Right now, the non-ref debugging code in astobj2 is triggered by a mix of
AST_DEVMODE and AO2_DEBUG and both get set if you want to run the test
framework. I've noticed though that the inclusion of the debugging code
can actually hide problems as well as highlight them, especially related to
