Merged revisions 119929 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.4

........
r119929 | murf | 2008-06-03 08:49:46 -0600 (Tue, 03 Jun 2008) | 16 lines

as per http://lists.digium.com/pipermail/asterisk-users/2008-June/212934.html,
which is a message from Philipp Kempgen, requesting that the WARNING
that an extension is empty be reduced to a NOTICE or less, as empty
extensions are syntactically possible, and no big deal.

With which I agree, and have removed that WARNING message entirely.
I think it is not necessary to see this message. It didn't 
state that a NoOp() was inserted automatically on your behalf,
and really, as users, who cares? Why freak out dialplan writers
with unnecessary warnings? The details of the machinations a compiler goes
thru to produce working assembly code is of little interest
to most programmers-- we will follow the unix principal of
doing our work silently.



........


git-svn-id: http://svn.digium.com/svn/asterisk/trunk@119930 f38db490-d61c-443f-a65b-d21fe96a405b

1 files changed, 0 insertions, 6 deletions

diff --git a/res/ael/pval.c b/res/ael/pval.c
index c1d20f608..fa9625a3d 100644
--- a/res/ael/pval.c
+++ b/res/ael/pval.c
@@ -4108,12 +4108,6 @@ void ast_compile_ael2(struct ast_context **local_contexts, struct ast_hashtab *l
 						exten-> return_target = np2;
 					}
 					/* is the last priority in the extension a label? Then add a trailing no-op */
-					if( !exten->plist_last )
-					{
-						ast_log(LOG_WARNING, "Warning: file %s, line %d-%d: Empty Extension!\n",
-								p2->filename, p2->startline, p2->endline);
-					}
-					
 					if ( exten->plist_last && exten->plist_last->type == AEL_LABEL ) {
 						struct ael_priority *np2 = new_prio();
 						np2->type = AEL_APPCALL;