Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!convex!convex.COM From: tchrist@convex.COM (Tom Christiansen) Newsgroups: comp.lang.perl Subject: Re: (*(dump = GNU ? unexec : undump))("perl.$$"); Message-ID: <100250@convex.convex.com> Date: 25 Feb 90 11:36:15 GMT References: <100236@convex.convex.com> <7166@jpl-devvax.JPL.NASA.GOV> Sender: news@convex.com Reply-To: tchrist@convex.COM (Tom Christiansen) Organization: CONVEX Software Development, Richardson, TX Lines: 26 >In other words, you'll have to be rather persuasive to get me to include >unexec() in the official perl. That's quite ok. I wasn't necessarily advocating including unexec() in official perl. I was just being lazy: I know that unexec() has been ported to the Convex's weird multi-threaded a.out format, but that undump.c hasn't. I was just looking for the path of least resistance. I know I really should port undump so that it can be used as a general tool. >Am I getting sufficiently grouchy in my old age? By no means. It's up to you as the language's designer, creator, and maintainer to stave off as many of the weird enhancement requests people may make as you can. I, for one, thank you for that. Otherwise the language will become more and more recherche until it's lost all semblance of common substance. While to some people it's already pathologically eclectic, to me at least it is not unusably so. It all still sort of makes sense taken in an lwallian context, if you know what I mean. --tom -- Tom Christiansen {uunet,uiucdcs,sun}!convex!tchrist Convex Computer Corporation tchrist@convex.COM "EMACS belongs in : Editor too big!"