Req #45913 [Opn->Sus]: include() environment during eval()

Edit report at https://bugs.php.net/bug.php?id=45913&edit=1 ID: 45913 Updated by: cmb@php.net Reported by: ganswijk at xs4all dot nl Summary: include() environment during eval() -Status: Open +Status: Suspended Type: Feature/Change Request -Package: Feature/Change Request +Package: *General Issues Operating System: irrelevant PHP Version: 5.3CVS-2008-08-25 (CVS) Block user comment: N Private report: N New Comment: Thank you for your interest in PHP and for submitting a feature request. Please be aware that due to the magnitude of change this request requires, it would be necessary to discuss it on PHP Internals list (internals@lists.php.net) as an RFC. Please read the guide about creating RFCs here: <https://wiki.php.net/rfc/howto>. If you haven't had experience with writing RFCs before, it is advised to seek guidance on the Internals list (<http://php.net/mailing-lists.php>) and/or solicit help from one of the experienced developers. Please do not consider this comment as a negative view on the merits of your proposal – every proposal which requires changes of certain magnitude, even the very successful and widely supported ones, must be done through the RFC process. This helps make the process predictable, transparent and accessible to all developers. Previous Comments: ------------------------------------------------------------------------ [2008-08-25 19:02:06] ganswijk at xs4all dot nl Description: ------------ I noticed that during the execution of an eval() the environment for an include() is kept the same as that of the original script executing the eval() but this probably often isn't the case, for example in the case of user contributed code to 'eval()'. To overcome this problem I currently use: $cwd=getcwd(); chdir(code-environment-of-code-to-eval); eval(code-to-eval); chdir($cwd); But perhaps this could be solved in a better way? Because in this I am assuming that the data environment is the same as the code environment for the code to eval(). BTW. I notice that PHP often makes no distinction between the current working directory for code and for data. I think that all the PHP definitions should be rewritten to make this distinction in all relevant cases. BTW2. Perhaps there should even be different workspaces for input and output data files... ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=45913&edit=1