[FiRe]

Will die automatically exit or do I have to include the exit(); statement after?

die("Hack attempt");
exit();

??

[hardcoded]

it would have been faster to see for yourself than ask here.

die()
echo "foobar"

[blaw]

Agreed with hardcoded, but if you really want to make sure, you could check the manual if it's a question about a function itself:

http://jp2.php.net/die

It says "die -- Equivalent to exit()"

[moronovich]

fyi, it's not like what most people imagine. because:

PHP Code:

print "Wrong params supplied";

exit();



<binary data here> 

you'll notice the binary data being still executed.

regards,

[frank1965]

DIE does what it means! Your script dies immediate! No further statements are processed!

[moronovich]

Originally Posted by frank1965

DIE does what it means! Your script dies immediate! No further statements are processed!

oops, emotional answer. but it's not the actual reality. just a while ago, there was a patch to use __HALT_PHP_PARSER__ constant to terminate the parser.

Code:

Index: Zend/zend_language_scanner.l
===================================================================
RCS file: /repository/ZendEngine2/zend_language_scanner.l,v
retrieving revision 1.124
diff -u -r1.124 zend_language_scanner.l
--- Zend/zend_language_scanner.l	7 Mar 2005 16:48:49 -0000	1.124
+++ Zend/zend_language_scanner.l	11 Mar 2005 23:47:11 -0000
@@ -1342,6 +1342,13 @@
 	return T_INLINE_HTML;
 }
 
+<INITIAL>"<?php __HALT_PHP_PARSER__; ?>"{NEWLINE}? {
+	long fpos = (yyin ? zend_stream_ftell(yyin TSRMLS_CC): 0) + (long)(yy_c_buf_p - (YY_CURRENT_BUFFER)->yy_ch_buf);
+	REGISTER_MAIN_LONG_CONSTANT("__HALT_PHP_PARSER__", fpos, CONST_CS);
+
+	yyterminate();
+}
+
 <INITIAL>"<?"|"<script"{WHITESPACE}+"language"{WHITESPACE}*"="{WHITESPACE}*("php"|"\"php\""|"\'php\'"){WHITESPACE}*">" {
 	HANDLE_NEWLINES(yytext, yyleng);
 	if (CG(short_tags) || yyleng>2) { /* yyleng>2 means it's not <? but <script> */