On May 19, 2008, at 7:26 PM, Philip Prindeville wrote: > Lonnie Abelbeck wrote: >> On May 19, 2008, at 12:30 PM, Darrick Hartman (lists) wrote: >> >> >>> Lonnie Abelbeck wrote: >>> >>>> On May 19, 2008, at 2:32 AM, Philip Prindeville wrote: >>>> >>>> >>>>> Darrick Hartman (lists) wrote: >>>>> >>>>>> [snip] >>>>>> Interesting. I usually use use the park and announce >>>>>> feature. So >>>>>> you >>>>>> just transfer the call to 1187 in your example, then have someone >>>>>> else >>>>>> dial 1188 (etc) to pick up the call. >>>>>> >>>>>> I'm just thinking how much of a pain in the butt it's going to >>>>>> be to >>>>>> redo all the Macro logic to a non-macro approach when the Macro >>>>>> function >>>>>> is deprecated. >>>>>> >>>>>> Darrick >>>>>> >>>>>> >>>>> Actually, I didn't find the new GoSub with arguments to be all >>>>> that >>>>> painful. It wasn't as bad as I thought it would be. >>>>> >>>>> -Philip >>>>> >>>> It appears that MACRO() is not going away, though deprecated. >>>> "for the sake of backwards compatibility it will not be removed" >>>> see >>>> below. >>>> >>>> From asterisk /tags/1.6.0-beta9/UPGRADE.txt >>>> >>>> 88 Macro() is now deprecated. If you need subroutines, you >>>> should >>>> use the >>>> >>> The developers typically remove the feature in the version after the >>> feature is marked as deprecated. I would expect this to be gone in >>> 1.8, >>> whenever that's released. So for 1.4 and 1.6, you're right that >>> Macro() >>> is still available. >>> >>> Darrick >>> >> >> I agree with you, removing deprecated features is the norm... but I >> read their description as... >> >> "we prefer you not to use macro() anymore, but because of all the >> grief we have been getting from removing long-standard features, we >> have decided to not remove macro() anytime soon" - my quote >> >> I predict 1.8 and 2.0 will include macro()... but, I may be >> wrong. :-) >> >> Lonnie >> > > I tried to submit a feature that required Macro(), and they spanked me > for it and made me resubmit after a rewrite of using Gosub(). > > Part of the reasoning was that the obsolescence of Macro() might get > moved up. > > -Philip
You got spanked before the "for the sake of backwards compatibility 'Macro()' will not be removed" got added to the notes, so maybe a new stratigery is in play. Beside the fact that the 1.6 GoSub() is the first that supports arguments. Lonnie ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
