[Asterisk-Dev] Moving towards macros..

[Brian West]

We only hold the lock on the object when needed.  (yes like gnome) it should
make deadlocks a thing of the past.  This should improve efficiency of
chan_sip since we only hold locks on objects we are needing.

bkw

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-
> bounces at lists.digium.com] On Behalf Of Matthew Boehm
> Sent: Sunday, December 26, 2004 10:29 AM
> To: Asterisk Developers Mailing List
> Subject: [Asterisk-Dev] Moving towards macros..
> 
> It seems that most of the code is moving towards macro calls. I just read
> this in the astobj.h file:
> 
> /*
> A set of macros implementing the asterisk object and container.  Macros
> are used for maximum performance, to support multiple inheritance, and
> to be easily integrated into existing structures without additional
> malloc calls, etc.
> */
> 
> Perhaps someone could explain how/why macros gain performance over regular
> function calls, the additional malloc calls, and the inheritance?
> 
> Thanks,
> Matthew
> 
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev