home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #18 / NN_1992_18.iso / spool / gnu / emacs / help / 3740 < prev    next >
Encoding:
Text File  |  1992-08-15  |  1022 b   |  23 lines
  1. Newsgroups: gnu.emacs.help
  2. Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!data.nas.nasa.gov!data!gumby
  3. From: gumby@Cygnus.COM (David V. Henkel-Wallace)
  4. Subject: Emacs Lisp: interactive calling of C subroutines
  5. In-Reply-To: acevedo@mit.edu's message of Mon, 10 Aug 1992 23:54:33 GMT
  6. References: <JBW.92Aug4234542@bigbird.bu.edu> <9208050442.AA27523@mole.gnu.ai.mit.edu>
  7.     <ACEVEDO.92Aug10195551@hippocrene.mit.edu>
  8. Sender: news@nas.nasa.gov (News Administrator)
  9. Organization: Cygnus Support, Palo Alto, California
  10. Date: 15 Aug 92 05:57:08
  11. Message-ID: <GUMBY.92Aug15055708@Cygnus.COM>
  12. Lines: 9
  13.  
  14.    Date: Mon, 10 Aug 1992 23:54:33 GMT
  15.    From: acevedo@mit.edu (Raul Acevedo)
  16.  
  17.    What other reasons?  I guess I can buy that maybe there's no easy way to
  18.    do it for all functions (maybe; I'm not familiar enough with the
  19.    internals of Emacs to know for sure), but what's so wrong with it?
  20.  
  21. It is hard for you to guarentee that some program you use won't depend
  22. on the functionality you change.  This can lead to subtle bugs.
  23.