<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:Courier New,courier,monaco,monospace,sans-serif;font-size:10pt"><div style="font-family: Courier New,courier,monaco,monospace,sans-serif; font-size: 10pt;">Well, a macro is the closest thing the dial plan has to a subroutine, and without that, we might as well be programming in Assembler (no subroutines, local variables, lots of goto's... sound familiar?).<br><br>Doug.<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Tilghman Lesher <tilghman@mail.jeffandtilghman.com><br>To: Asterisk Users Mailing List - Non-Commercial Discussion <asterisk-users@lists.digium.com><br>Sent: Friday, July 11, 2008 7:20:40 AM<br>Subject: Re: [asterisk-users] Asterisk as an IVR solution<br><br>
On Friday 11 July 2008 01:28:34 Douglas Garstang wrote:<br>> Well I can tell you that it makes a difficult programming environment, just<br>> a little more difficult. It means I can't implement a menu as a single<br>> reusable piece of code inside a macro.<br><br>That's the point. A Macro is NOT a subroutine. It's like saying that you<br>can't effectively hammer a nail with a screwdriver, and therefore you think<br>the screwdriver has a known problem. There's nothing wrong with the<br>screwdriver; it simply is the wrong tool for the job.<br><br>-- <br>Tilghman<br><br>_______________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br><br>AstriCon 2008 - September 22 - 25 Phoenix, Arizona<br>Register Now: <a href="http://www.astricon.net" target="_blank">http://www.astricon.net</a><br><br>asterisk-users mailing
list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></div></div></div><br>
</body></html>