Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:771
Return-Path: <rasmus@lerdorf.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17770 invoked from network); 7 Apr 2003 21:35:22 -0000
Received: from unknown (HELO www.lerdorf.com) (66.93.78.119)
  by pb1.pair.com with SMTP; 7 Apr 2003 21:35:22 -0000
Received: from rasmus2.corp.yahoo.com (rasmus2.corp.yahoo.com [207.126.232.175])
	by www.lerdorf.com (8.12.9/8.12.9/Debian-1) with ESMTP id h37LZL7q007922
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <internals@lists.php.net>; Mon, 7 Apr 2003 14:35:21 -0700
Date: Mon, 7 Apr 2003 13:35:27 -0700 (PDT)
To: internals@lists.php.net
Message-ID: <Pine.LNX.4.44.0304071328360.876-100000@thinkpad.lerdorf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: zend_eval_string() question
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Could anybody explain the difference between calling:

zend_eval_string(source, NULL, description)

and

zval retval;
zend_eval_string(source, &retval, description)

It looks to me like if a retval zval is provided there is some sort of 
implicit return value pasted onto the script, but it means that a simple 
string like:  echo "123";
causes a parse error whereas: print "123";
works just fine.  That's pretty confusing.

-Rasmus