Xref: utzoo gnu.emacs.help:504 comp.emacs:9677 Path: utzoo!utgpu!watserv1!watmath!uunet!peregrine!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!INEL.GOV!dob From: dob@INEL.GOV (David Brooks) Newsgroups: gnu.emacs.help,comp.emacs Subject: 'new' byte compiler Message-ID: <9012060015.AA03373@jonty.inel.gov> Date: 6 Dec 90 00:15:55 GMT Sender: daemon@tut.cis.ohio-state.edu Followup-To: gnu.emacs.help Organization: Gatewayed from the GNU Project mailing list help-gnu-emacs@prep.ai.mit.edu Lines: 31 First, thanks for all who helped with my recent questions on emacs 18.55 and the Cray. i received patches from Bob Jones at UTexas, though i haven't quite fathomed the mysteries of C compiling on our system. our local Cray person is going to be helping me get it built; fortunately, there's a lot of interested in using Emacs at our site. my question: i seem to remember seeing something about a 'new' and more efficient byte compiler. could i get some info and feedback on this, please? is it safe? recommended? are there lots of good experiences with it, or bad? should i recompile everything with it, or just the things i don't mind trashing a little bit? i'm sure it's wonderful, but i'm kind of into reality... if it's great, how do i get it? and who do i thank for it? does it bake a good pizza? i'm running out of questions here. i really wish i could contribute to this group, as there have been so many helpful suggestions and code fragments. i'm involved in teaching Emacs as a developement environment and productivity tool locally, and there seems to be a demand for it. perhaps spreading the word will be thanks enough. dlb ------------------------------------------------------------------------------ David L. Brooks Idaho National Engineering Lab. INTERNET: dob@INEL.GOV POB 1625 MS 2603 Phone: (208) 526-0826 Idaho Falls, Id. 83415 FAX: (208) 526-9936 ------------------------------------------------------------------------------ Brought to you by Super Global Mega Corp .com