Howdy! I know there have been lots of questions, answers, and discussions about the future of MacPerl under OS X, but somehow none of them have done it for me. This is probably due to my total ignorance. I wonder if those of you with the shiny new MacOS X beta on your disks and a "Certified MacPerl Developer" sterling silver memorial buckle on your belts will give it one more go. 1) What is the newline character under OS X? 2) I deleted a rambling discourse on this; so to say it briefly, anyone who has run Perl under Windows knows why MacPerl is so wonderful. Developing short little scripts in the simple integrated MacPerl enviroment is quick, easy, and intuitive. Droplets fit nicely into both the Perl and Macintosh paradigms. Unless MacOS X eliminates drag and drop, point and click as the primary interface, I see just as much a need for the MacPerl application under OS X as under OS 1-9 (sez he who still has a copy of OS 1). It seems to me this is entirely separate from the whole issue of porting the interpreter per se; the application consists of the basic interpreter plus a simple, intuitive development environment plus the droplet code. OS X may change how best to port the interpreter, but it seems to me that the development environment and the droplet code are as useful as ever. Am I missing something? 3) Is it anticipated that all web serving and CGI programming will be done in an essentially Unix environment? Will the need for "save as CGI script" have past? 4) Will the AppleEvents interapplication interface be entirely replaced by a Unix stdin/stdout interface? 5) Is this the right place for MacOS X/MacPerl questions? If not, where? -David Steffen- David Steffen, Ph.D. President, Biomedical Computing, Inc. <http://www.biomedcomp.com/> Phone: (713) 610-9770 FAX: (713) 610-9769 E-mail: steffen@biomedcomp.com # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org