Darren J Moffat writes: > > HOWEVER, I would really, really have preferred to see PSARC discourage > > or even disallow the use of perl for "core platform technology". (This > > goes for Python, Tcl, and some of the other scripting languages that > > abound these days.) > > I don't think ARC is the place to do this. It isn't really architecture > but more implementation. The C-Teams for the various consolidations > together with the OpenSolaris communities that represent the > consolidations can create such rules if they wish.
I disagree. The burden placed on the overall system due to the use of Perl (or any other implementation choice) _is_ an architectural issue. This is the same thing as allowing people to place new files whereever they want in the file system rather than following filesystem(5) -- if we allow core system components to be written to drag in arbitrary baggage, then arbitrary baggage is exactly what we'll get. The only problem here is that there's no precedent. Someone with a good set of asbestos underwear should certainly draft up and file an ARC case to set that precedent. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
