On Thu, 22 Oct 1998, Chris Nandor wrote: > At 15.16 -0400 1998.10.22, Richard Gordon wrote: > >I know that if I avoid Mac-specific things, my Perl stuff should > >theoretically function under both Linux and Solaris with minimal tweaking, > >but I am wondering what to expect in terms of likely complications? Would I > >be better off trading comfort for efficiency and just doing all development > >in mkLinux to begin with? Thanks for any help you may have to offer. > > There is a document dealing with most of the issues: > > http://www.perl.com/CPAN/doc/manual/html/pod/perlport.html > > But in general, it is much easier to go from Mac to Unix than the other way > around, so you shouldn't have too many problems in starting on the Mac and > developing for Solaris or MkLinux. Note that CGI development under MacOS is limited because MacPerl is not threaded, and MacOS is not pre-emptively multitasking. Script behavior may be different when you call the same script multiple times rapidly, or if one script got called while another was running, and so on. However, for non-CGI portions of the code, MacPerl is equally fit. The ideal situation, I think, is to network two machines together, one running Linux/MkLinux/LinuxPPC and one running MacOS. Run Apache on the first, client on the second, develop either through a telnet or by ftp. If speed becomes an issue, you may need to look at web servers that have an embedded Perl engine and which can cache performance critical modules. (There seem to be many of these available, going by names such as FastCGI, ePerl, and modperl aka the CPAN Apache bundle.) But in choosing this route, you will probably limit your testing options to the same webserver/engine combo, and perhaps limit platform options as well. But that decision can wait until after at least preliminary testing. Good luck. -- MattLangford ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch