RE: [PHP4BETA] 4.0 B3 RC 3 - output.c

I agree. I'd prefer seeing one modules workspace instead of one for each module. Andi At 08:39 PM 11/9/99 -0500, Peter Bowen wrote:

Yes, php4ts.dsw uses the ts version of php4dll to build the CGI version. The following files are duplicate/unnecessary as of RC3, by my count: php4.dsw php4ext.dsw regex.dsw libzend.dsw php4dll.dsp php4.dsp php4isapi.dsp (in two different directories, identical copies) and the dl\mssql directory can go away (has the PHP3 MS Sql module in it). I am also a proponent of the idea that each module should have one, and only one project that it is in, and all module projects be put into the php_module workspace. Under this plan, there would be two workspaces: php4ts.dsw for the main PHP4 sapi DLLs and the CGI, and php_modules.dsw for all the loadable modules. Bindlib_w32 also has its own, independant, project and workspace. Compiling for Win32 would be much more simple with fewer workspaces and projects. Thanx. Peter -----Original Message----- From: rubys@us.ibm.com [mailto:rubys@us.ibm.com] Sent: Tuesday, November 09, 1999 7:18 PM To: Peter Bowen; 'Andi Gutmans'; php4beta@lists.php.net' Subject: RE: [PHP4BETA] 4.0 B3 RC 3 - output.c Andi wrote: We were actually thinking of nuking the non-TS version as it adds a bit of maintenance overhead and our aim is for people to use it as an ISAPI module and not CGI binary on Win32. In any case there shouldn't be more than one project covering any non-trivial amount of code. If necessary, continuing to support multiple configurations within a project is a possibility, but I would recommend against it unless there were an *extremely* compelling reason as such choices tend to grow exponentially. Hopefully there is nothing to preclude a php4/sapi/apache/apache.dsp from being written... Personally, I love the CGI version for debugging... TS adds some overhead but with the overhead of CGI the kind of projects using it would probably not suffer from the slight performance decrease of TS. From what I have seen, I can't imagine that it would be noticable. Peter wrote: As of beta 3 rc 3 the ISAPI DLL and php_mssql DLL don't work together correctly. I haven't had a chance to try to debug it, but I know that the CGI version with MS SQL works fine, and the ISAPI version alone works fine. The TS version builds a CGI executable just fine. This is independent of TS vs non-TS, right? In other words, if php4dll.dsp were eliminated, you can still build a working CGI version of MS SQL with php4ts.dsp, right? -- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net For additional commands, e-mail: php4beta-help@lists.php.net To contact the list administrators, e-mail: php4beta-admin@lists.php.net

--- Andi Gutmans <andi@zend.com> http://www.zend.com/