bull9.html 59 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697989910010110210310410510610710810911011111211311411511611711811912012112212312412512612712812913013113213313413513613713813914014114214314414514614714814915015115215315415515615715815916016116216316416516616716816917017117217317417517617717817918018118218318418518618718818919019119219319419519619719819920020120220320420520620720820921021121221321421521621721821922022122222322422522622722822923023123223323423523623723823924024124224324424524624724824925025125225325425525625725825926026126226326426526626726826927027127227327427527627727827928028128228328428528628728828929029129229329429529629729829930030130230330430530630730830931031131231331431531631731831932032132232332432532632732832933033133233333433533633733833934034134234334434534634734834935035135235335435535635735835936036136236336436536636736836937037137237337437537637737837938038138238338438538638738838939039139239339439539639739839940040140240340440540640740840941041141241341441541641741841942042142242342442542642742842943043143243343443543643743843944044144244344444544644744844945045145245345445545645745845946046146246346446546646746846947047147247347447547647747847948048148248348448548648748848949049149249349449549649749849950050150250350450550650750850951051151251351451551651751851952052152252352452552652752852953053153253353453553653753853954054154254354454554654754854955055155255355455555655755855956056156256356456556656756856957057157257357457557657757857958058158258358458558658758858959059159259359459559659759859960060160260360460560660760860961061161261361461561661761861962062162262362462562662762862963063163263363463563663763863964064164264364464564664764864965065165265365465565665765865966066166266366466566666766866967067167267367467567667767867968068168268368468568668768868969069169269369469569669769869970070170270370470570670770870971071171271371471571671771871972072172272372472572672772872973073173273373473573673773873974074174274374474574674774874975075175275375475575675775875976076176276376476576676776876977077177277377477577677777877978078178278378478578678778878979079179279379479579679779879980080180280380480580680780880981081181281381481581681781881982082182282382482582682782882983083183283383483583683783883984084184284384484584684784884985085185285385485585685785885986086186286386486586686786886987087187287387487587687787887988088188288388488588688788888989089189289389489589689789889990090190290390490590690790890991091191291391491591691791891992092192292392492592692792892993093193293393493593693793893994094194294394494594694794894995095195295395495595695795895996096196296396496596696796896997097197297397497597697797897998098198298398498598698798898999099199299399499599699799899910001001100210031004100510061007100810091010101110121013101410151016101710181019102010211022102310241025102610271028102910301031103210331034103510361037103810391040104110421043104410451046104710481049105010511052105310541055105610571058105910601061106210631064106510661067106810691070107110721073107410751076107710781079108010811082108310841085108610871088108910901091109210931094109510961097109810991100110111021103110411051106110711081109111011111112111311141115111611171118111911201121112211231124112511261127112811291130113111321133113411351136113711381139114011411142114311441145
  1. <!-- This HTML file has been created by texi2html 1.30
  2. from bull9.texi on 28 January 1995 -->
  3. <TITLE>GNU's Bulletin, vol. 1 no. 9 - June, 1990</TITLE>
  4. <H1>GNU's Bulletin, vol. 1 no. 9 - June, 1990</H1>
  5. <P>
  6. <HR>
  7. <P>
  8. The GNU's Bulletin is the semi-annual newsletter of the
  9. Free Software Foundation, bringing you news about the GNU Project.
  10. <P>
  11. Free Software Foundation, Inc. Telephone: (617) 876-3296 <BR> 675
  12. Massachusetts Avenue Electronic mail: gnu@prep.ai.mit.edu <BR>
  13. Cambridge, MA 02139 USA
  14. <P>
  15. <HR>
  16. <P>
  17. <H1><A NAME="SEC3" HREF="bull9_toc.html#SEC3">GNU's Who</A></H1>
  18. <P>
  19. <B>Joseph Arceneaux</B> is developing Emacs Version 19. <B>Jim
  20. Kingdon</B> is working on GDB. <B>Michael Rowan</B> is writing a
  21. <CODE>login</CODE> replacement to work with <CODE>xdm</CODE>. <B>Roland
  22. McGrath</B> will again be on the payroll starting in July; he is finishing
  23. up the C library and maintains GNU make. <B>David MacKenzie</B> has
  24. been hired as a summer programmer and is maintaining the file
  25. utilities.<P>
  26. <B>Brian Fox</B> is maintaining various programs that he has written,
  27. including the <CODE>readline</CODE> library, the <CODE>makeinfo</CODE> and Info
  28. programs, BASH, and the new GNU <CODE>finger</CODE>. <B>Jay Fenlason</B>
  29. continues with the GNU spreadsheet, Oleo, as well as maintaining
  30. <CODE>tar</CODE>, <CODE>sed</CODE> and the GNU assembler.<P>
  31. <B>Mike Haertel</B> continues work on the C interpreter; he is also
  32. maintaining and improving the "bin" utilities and species of
  33. <CODE>grep</CODE>. <B>David Lawrence</B>, who works for us at the Rensselaer
  34. Polytechnic Institute, is maintaining the Lisp libraries for Emacs.
  35. <B>Kathy Hargreaves</B> is now working on Ghostscript, having just
  36. finished making the regular expression routines mostly POSIX-compliant.
  37. <B>Karl Berry</B> is also working on Ghostscript.<P>
  38. <B>Amy Gorin</B> has been hired as a documentation writer, starting with
  39. the manual for <CODE>tar</CODE>. <B>Diane Barlow Close</B> continues work on
  40. the <CITE>BASH Programming Manual</CITE>. <B>Grace Sylvan</B> is writing the
  41. <CITE>GNU C Reference Manual</CITE>.<P>
  42. <B>S. Opus Goldstein</B> is still doing a great job running our office.
  43. <B>Erica Brigid</B> is answering phone calls, handling correspondence,
  44. and making distribution tapes. <B>Robert J. Chassell</B>, our
  45. Treasurer, is working on an elementary introduction to programming in
  46. Emacs Lisp, in addition to the many Foundation issues not related to
  47. programming.<P>
  48. <B>Richard Stallman</B> continues as a volunteer who does countless tasks,
  49. including refining the C compiler, GNU Emacs, etc., and their
  50. documentation. Finally, volunteer <B>Len Tower</B> remains our
  51. electronic JOAT (jack-of-all-trades), handling mailing lists and
  52. gnUSENET, information requests, and the like.<P>
  53. <HR>
  54. <P>
  55. <H3><A NAME="SEC4" HREF="bull9_toc.html#SEC4">GNU's Bulletin</A></H3>
  56. <P>
  57. Copyright (C) 1990 Free Software Foundation, Inc.
  58. <P>
  59. Written by: Michael Rowan, Robert J. Chassell, Richard Stallman,
  60. <BLOCKQUOTE>
  61. Leonard H. Tower Jr., and Michael Bloom
  62. </BLOCKQUOTE>
  63. <P>
  64. Illustrations: Etienne Suvasa
  65. <P>
  66. Japanese Edition: Mieko Hikichi and Nobuyuki Hikichi
  67. <P>
  68. <BLOCKQUOTE>
  69. Permission is granted to anyone to make or distribute verbatim copies of
  70. this document as received, in any medium, provided that the copyright
  71. notice and permission notice are preserved, and that the distributor
  72. grants the recipient permission for further redistribution as permitted
  73. by this notice.</BLOCKQUOTE>
  74. <P>
  75. <H1><A NAME="SEC5" HREF="bull9_toc.html#SEC5">What Is the Free Software Foundation?</A></H1>
  76. <P>
  77. The Free Software Foundation is dedicated to eliminating restrictions on
  78. copying, redistribution, understanding, and modification of computer
  79. programs. We do this by promoting the development and use of free
  80. software in all areas of computer use. Specifically, we are putting
  81. together a complete integrated software system named "GNU" (GNU's Not
  82. Unix) that will be upwardly compatible with Unix. Some large parts of
  83. this system are already working, and we are distributing them
  84. now.<P>
  85. The word "free" in our name refers to two specific freedoms: first,
  86. the freedom to copy a program and give it away to your friends and
  87. co-workers; second, the freedom to change a program as you wish, by
  88. having full access to source code. Furthermore, you can study the
  89. source and learn how such programs are written. You may then be able to
  90. port it, improve it, and share your changes with others.<P>
  91. Other organizations distribute whatever free software happens to be
  92. available. By contrast, FSF concentrates on development of new free
  93. software, working towards a GNU system complete enough to eliminate the
  94. need to purchase a proprietary system.<P>
  95. Besides developing GNU, the Foundation has secondary functions:
  96. producing tapes and printed manuals of GNU software, carrying out
  97. distribution, and accepting gifts to support GNU development. We are
  98. tax exempt; you can deduct donations to us on your tax returns. Our
  99. development effort is funded partly from donations and partly from
  100. distribution fees. Note that the distribution fees purchase just the
  101. service of distribution: you never have to pay anyone license fees to
  102. use GNU software, and you always have the freedom to make your copy from
  103. a friend's computer at no charge (provided your friend is
  104. willing).<P>
  105. The Foundation also maintains a Service Directory: a list of people who
  106. offer service for pay to users of GNU programs and systems. The Service
  107. Directory is located in file <TT>`etc/SERVICE'</TT> in the GNU Emacs
  108. distribution. Service can mean answering questions for new users,
  109. customizing programs, porting to new systems, or anything else. Contact
  110. us if you want to be listed or wish a copy.<P>
  111. After we create our programs, we continually update and improve them.
  112. We release between 2 and 20 updates a year for each program. Doing this
  113. while developing new programs takes a lot of work, so any donations of
  114. pertinent source code and documentation, machines, labor, or money are
  115. always appreciated.<P>
  116. The board of the Foundation is: Richard Stallman, President; Robert J.
  117. Chassell, Treasurer; Gerald J. Sussman, Harold Abelson and Leonard H.
  118. Tower Jr., Directors.\vfil
  119. <P>
  120. <H1><A NAME="SEC6" HREF="bull9_toc.html#SEC6">What Is Copyleft?</A></H1>
  121. <P>
  122. In the previous section entitled "What Is the Free Software
  123. Foundation?" we state that "you never have to pay anyone license fees
  124. to use GNU software, and you always have the freedom to make your copy
  125. from a friend's computer at no charge." What exactly do we mean by
  126. this, and how do we make sure that it stays true?<P>
  127. The simplest way to make a program free is to put it in the public
  128. domain. Then people who get it from sharers can share it with others.
  129. But this also allows bad citizens to do what they like to do: sell
  130. binary-only versions under typical don't-share-with-your-neighbor
  131. licenses. They would thus enjoy the benefits of the freeness of the
  132. original program while withholding these benefits from the users. It
  133. could easily come about that most users get the program this way, and
  134. our goal of making the program free for <EM>all</EM> users would have been
  135. undermined.<P>
  136. To prevent this from happening, we don't normally place GNU programs in
  137. the public domain. Instead, we protect them by what we call
  138. <DFN>copylefts</DFN>. A copyleft is a legal instrument that makes everybody
  139. free to copy a program as long as the person getting the copy gets with
  140. it the freedom to distribute further copies, and the freedom to modify
  141. their copy (which means that they must get access to the source code).
  142. Typical software companies use copyrights to take away these freedoms;
  143. now software sharers use copylefts to preserve these freedoms.<P>
  144. The copyleft used by the GNU Project is made from a combination of a
  145. copyright notice and the <DFN>GNU General Public License</DFN>. The
  146. copyright notice is the usual kind. The General Public License is a
  147. copying license which basically says that you have the freedoms we want
  148. you to have and that you can't take these freedoms away from anyone
  149. else. (The actual document consists of several pages of rather
  150. complicated legalbol that our lawyer said we needed.) The complete
  151. license is included in all GNU source code distributions and many
  152. manuals. We will send you a copy on request.<P>
  153. We encourage others to copyleft their programs using the General Public
  154. License; basically programs only need to include a few sentences stating
  155. that the license applies to them. Specifics on using the License
  156. accompany it, so refer there for details.<P>
  157. <BLOCKQUOTE>
  158. <EM>"As we enjoy great advantages from the inventions of others, we
  159. should be glad of an opportunity to serve others by any invention of
  160. ours."</EM></BLOCKQUOTE>
  161. <P>
  162. --Benjamin Franklin
  163. <P>
  164. <H1><A NAME="SEC7" HREF="bull9_toc.html#SEC7">GNUs Flashes</A></H1>
  165. <P>
  166. <UL>
  167. <LI>
  168. <B>Emacs Lisp Reference Manual</B>
  169. <P>
  170. It's here! We are now shipping the long awaited <CITE>GNU Emacs Lisp
  171. Reference Manual</CITE>. It describes the GNU Emacs Lisp programming language
  172. in great detail. The manual is about 550 pages and can be ordered from
  173. us for $50. Early drafts of this manual are still floating around from
  174. several years ago, mostly at <CODE>ftp</CODE> sites. We strongly urge you to
  175. update to the new version since the improvements are innumerable. (As
  176. always you can <CODE>ftp</CODE> the manual from the usual sources.)<P>
  177. <LI>
  178. <B>Smalltalk</B>
  179. <P>
  180. GNU now has a Smalltalk system. It was written by Steve Byrne. We
  181. currently have Version 1.0 available on <CODE>prep.ai.mit.edu</CODE>.
  182. Version 1.1 should be out soon. GNU Smalltalk is based on the
  183. <CITE>"blue book"</CITE> definition of the Smalltalk language. It is
  184. written in highly portable C and runs on a number of UNIX machines
  185. (Version 1.1 will offer more ports than the current version, which only
  186. runs on 4 or 5 machines). A graphical user interface is also planned.
  187. Response to the system has generally been very favorable, especially for
  188. a young system.<P>
  189. <LI>
  190. <B>GNU Finger</B>
  191. <P>
  192. GNU Finger is now available. This is a daemon--based finger program
  193. that polls all of the hosts at a site for finger--related information.
  194. With GNU Finger, information can now be retrieved for a user on a
  195. site--wide basis instead of a host--specific basis. Our finger also
  196. displays bitmaps of users' faces where available. See "GNU Finger"
  197. under "GNU Project Status Report" for more information.<P>
  198. <LI>
  199. <B>Donation from the Open Software Foundation</B>
  200. <P>
  201. We want to thank OSF for yet another donation of $25,000. It is also
  202. planning significant improvements for the GNU Assembler and
  203. binutils.<P>
  204. <LI>
  205. <B>Long-named options</B>
  206. <P>
  207. As we have mentioned before, we are adding long-named options to many of
  208. our utilities. We have done this by adding functionality to our
  209. <CODE>getopt</CODE> library. <CODE>getopt_long</CODE> can now be used to parse long
  210. options as well as the normal single-lettered options allowed by the
  211. standard <CODE>getopt</CODE>. For example, instead of remembering whether to
  212. use <CODE>-v</CODE> or <CODE>-V</CODE>, you can use <CODE>+verbose</CODE> (or any
  213. unambiguous abbreviation) in all programs. Eventually we hope to
  214. provide command-line completion for long option names.<P>
  215. <LI>
  216. <B>DBM replacement</B>
  217. <P>
  218. Version 1.3 of our <CODE>gdbm</CODE> library has been released. It is a
  219. replacement for the <CODE>dbm</CODE> and <CODE>ndbm</CODE> libraries. Our
  220. <CODE>gdbm</CODE> database is stored in one file which contains no large
  221. holes, supports read/write interlocking, handles keys and data of
  222. unlimited size, and provides routines supporting both the <CODE>ndbm</CODE>
  223. and <CODE>dbm</CODE> interfaces. These features separate <CODE>gdbm</CODE> from its
  224. proprietary predecessors.<P>
  225. </UL>
  226. <P>
  227. <H1><A NAME="SEC8" HREF="bull9_toc.html#SEC8">Possible New Terms for GNU Libraries</A></H1>
  228. <P>
  229. by Richard Stallman
  230. <P>
  231. We are considering changing the distribution terms for some GNU
  232. libraries, such as <CODE>libg++</CODE> and the (as yet unreleased) C
  233. library.<P>
  234. The GNU General Public License was designed for utility programs, such
  235. as Emacs and GCC. It makes a sharp distinction between using the
  236. program and copying any part of it: Any program containing any
  237. significant portion of the GNU program must be freely redistributable to
  238. be permitted at all. However, merely using the program (for example, an
  239. editor) imposes no restriction on the work that is done with it.<P>
  240. Libraries blur the distinction between modifying or adding to a program
  241. and simply using it. Linking a program with a library, without changing
  242. the library, is in some sense simply using the library, and analogous to
  243. running a utility program or application program. However, in a textual
  244. and legal sense, the linked executable is a combined work which is a
  245. derivative of the original library, and the ordinary General Public
  246. License treats it as such. As a result, developers of proprietary
  247. software have not used the GNU libraries.<P>
  248. The goal of the Free Software Foundation is to promote the freedom to
  249. share software, for software developers and for users; we develop
  250. software for sharing as a means to this end. As a pragmatic matter, if
  251. the conditions for use of this software are such that most developers
  252. choose not to use it, then we don't achieve the goal. At the same time,
  253. if the conditions are so loose that people can use the software without
  254. much additional sharing, then we don't achieve the goal.<P>
  255. It seems that the ordinary General Public License is too restrictive for
  256. libraries, and is discouraging their use rather than encouraging
  257. further sharing. However, it would not be best to do what
  258. proprietary software developers ask us to do--to permit completely
  259. unrestricted use of our libraries in proprietary software--because
  260. then the end users of that software wouldn't get a jot of additional
  261. freedom as a consequence of the use of our library. We need to find a
  262. proper middle ground.<P>
  263. Our idea is to require the distributor of the proprietary executable to
  264. make the source to our library available along with the object files for
  265. the rest of the application. The user could then recompile the library
  266. (perhaps with changes) and relink to get a usable program. This way the
  267. user will, in some sense, get the benefit of the free status of the
  268. library within the executable.<P>
  269. However, not all the details are settled, so we aren't announcing the
  270. precise new library terms just yet.<P>
  271. <H1><A NAME="SEC9" HREF="bull9_toc.html#SEC9">League for Programming Freedom</A></H1>
  272. <P>
  273. by Michael Bloom and Richard Stallman
  274. <P>
  275. The League for Programming Freedom is an organization of people who
  276. oppose the attempt to monopolize common user interfaces through "look
  277. and feel" copyright lawsuits. Some of us are programmers who worry
  278. that such monopolies will obstruct our work. Some of us are users who
  279. want new computer systems to be compatible with the interfaces we
  280. know.<P>
  281. "Look and feel" lawsuits aim to create a new class of
  282. government-enforced monopolies that would be broader in scope than ever
  283. before. Such a system of user-interface copyright would impose
  284. gratuitous incompatibility, reduce competition, and stifle
  285. innovation.<P>
  286. We in the League hope to prevent these problems by preventing
  287. user-interface copyright. The League is not opposed to copyright law as
  288. it was understood until 1986--i.e., copyright on particular programs.
  289. Our aim is to stop changes in the copyright system, which would take
  290. away programmers' traditional freedom to write new programs that are
  291. compatible with existing programs and practices.<P>
  292. The League for Programming Freedom will act against the doctrine
  293. behind look-and-feel suits by any means consistent with the law and
  294. intellectual liberty. We will write editorials, talk with public
  295. officials, file amicus curiae briefs with the courts, and boycott
  296. egregious offenders. If you have other ideas, please suggest
  297. them.<P>
  298. The League members are now voting on the question of opposing software
  299. patents, which threaten to make every design decision in software
  300. development a chance for a lawsuit. The League's founders consider
  301. software patents potentially more dangerous than look-and-feel
  302. copyright, and the members voting so far seem to agree. Final results
  303. will be known at the beginning of June.<P>
  304. The more members we have, the more effective we will be. Even if you
  305. cannot donate any time, simply joining will make a difference.<P>
  306. The dues are $42 for professionals, $21 for others, except students
  307. whose dues are $10.50. To join, write to:<P>
  308. <PRE>
  309. League for Programming Freedom, 1 Kendall Square #143,
  310. P.O.Box 9171, Cambridge, MA 02139, USA. Phone: (617) 492--0023.
  311. <CODE>league@prep.ai.mit.edu</CODE>
  312. </PRE>
  313. <P>
  314. Note that the League for Programming Freedom is a separate organization
  315. from the Free Software Foundation; please direct all League inquiries to
  316. the above address, not to the Foundation.<P>
  317. <H1><A NAME="SEC10" HREF="bull9_toc.html#SEC10">Free Software Support</A></H1>
  318. <P>
  319. The Free Software Foundation develops and distributes freely available
  320. software. Our goal is to help computer users as a community. We
  321. envision a world in which software is freely redistributable. This
  322. means software will be sold at a competitive market price rather than a
  323. monopoly established price; often, it will be given away. We see
  324. programmers as providing a service, much as doctors and lawyers now
  325. do--both medical knowledge and the law are freely redistributable
  326. entities for which the practitioners charge a distribution and service
  327. fee.<P>
  328. To help you find support and other consulting services, we maintain a
  329. list of people who offer such services. We call this list the GNU
  330. Service Directory. This list is contained in the file
  331. <TT>`etc/SERVICE'</TT> in the GNU Emacs distribution. If you want to offer
  332. services, you can use this list to help make yourself known. (Contact us
  333. if you would like a copy of this directory or wish to be
  334. included.)<P>
  335. Most of the listings in the GNU Service Directory are for individuals,
  336. but one is for Cygnus Support, which is the first for-profit corporation
  337. that we know of that provides support <EM>only</EM> for free software.
  338. Their address is <CODE>info@cygnus.com</CODE> or Cygnus Support, 814
  339. University Ave., Palo Alto, CA 94301. FSF is not affiliated with Cygnus
  340. Support, but we hope that Cygnus Support is a harbinger of the
  341. future.<P>
  342. If you find a deficiency in any GNU software, we want to know. We
  343. maintain a considerable number of Internet mailing lists for making
  344. announcements, reporting bugs and for asking questions. The Emacs
  345. and GCC Manuals have chapters explaining where to send bug reports and
  346. what information to put in them. Incidentally, on the larger lists, it
  347. is not surprising to see an enquiry answered on the same day it is
  348. posted.<P>
  349. These mailing lists are also gatewayed into USENET news. If your site
  350. receives USENET, you can follow these discussions using news software.
  351. To find out more about the <CODE>gnu.*</CODE> newsgroups, ask your system
  352. administrator.<P>
  353. If you don't have Internet access, you can receive mail and USENET news
  354. with a UUCP connection. Contact either a system administrator at a
  355. local UUCP site, or UUNET Communications, which can set up a UUCP
  356. connection for a modest fee. (UUNET is a non-profit organization that
  357. provides network connections.) You can contact UUNET by e-mail at
  358. <CODE>info@uunet.uu.net</CODE> or by paper mail at:<P>
  359. <PRE>
  360. UUNET Communications Services, 3110 Fairview Park Drive -- Suite 570,
  361. Falls Church, VA 22042 Phone: (703) 876--5050
  362. </PRE>
  363. <P>
  364. When we receive a bug report, we will usually try to fix the problem in
  365. order to make the software better. This may help you in the long run;
  366. however, we may not provide you with immediate assistance. This is not
  367. and should not be our job. Our task is so large that we must focus on
  368. that which helps the community as a whole, such as developing and
  369. maintaining software and documentation. We mustn't let ourselves be
  370. sidetracked into helping individuals one by one. We do not have the
  371. resources. Thus, do tell us how an installation script doesn't work or
  372. where the documentation is unclear--but please don't ask us to help you
  373. install the software or figure out how to use it.<P>
  374. If your bug report does not evoke a solution from us, you may still get
  375. one from the many other users who read our bug reporting mailing lists.
  376. Otherwise, use the Service Directory.<P>
  377. <H1><A NAME="SEC11" HREF="bull9_toc.html#SEC11">GNU Project Status Report</A></H1>
  378. <P>
  379. <UL>
  380. <LI>
  381. <B>GNU Emacs</B>
  382. <P>
  383. GNU Emacs 18 is now stable. Only a few important bugs have been
  384. encountered since Version 18.55.<P>
  385. Berkeley is distributing GNU Emacs with the 4.3 distribution, and
  386. numerous companies also distribute it.<P>
  387. Version 18 maintenance continues and a new version, 18.56, is expected
  388. soon. It has no new features, however. Version 19 approaches release
  389. with a host of new features: before and after change hooks; X selection
  390. processing (including CLIPBOARD selections); scrollbars; support for
  391. European character sets; floating point numbers; per-buffer mouse
  392. commands; interfacing with the X resource manager; mouse-tracking;
  393. Lisp-level binding of function keys; and multiple X windows (`screens'
  394. to Emacs).<P>
  395. Thanks go to Alan Carroll and the people who worked on Epoch for
  396. generating initial feedback to a multi-windowed Emacs. Emacs 19
  397. supports two styles of multiple windows, one with a separate screen for
  398. the minibuffer, and another with a minibuffer attached to each
  399. screen.<P>
  400. More features of Version 19 are buffer allocation, which uses a new
  401. mechanism capable of returning storage to the system when a buffer is
  402. killed, and a new input system--all input now arrives in the form of
  403. Lisp objects.<P>
  404. Other features being considered for Version 19 include:
  405. <P>
  406. <UL>
  407. <LI>
  408. Associating property lists with regions of text in a buffer.<LI>
  409. Multiple font, color, and pixmaps defined by those properties.<LI>
  410. Different visibility conditions for the regions, and for the various
  411. windows showing one buffer.<LI>
  412. Incremental syntax analysis for various programming languages.<LI>
  413. Hooks to be run if point or mouse moves outside a certain range.<LI>
  414. Source-level debugging for Emacs Lisp.<LI>
  415. Incrementally saving undo history in a file, so that recover-file also
  416. reinstalls buffer's undo history.<LI>
  417. Static menu bars, and better pop-up menus.<LI>
  418. A more sophisticated emacsclient/server model, which would provide
  419. network transparent Emacs widget functionality.</UL>
  420. <P>
  421. <LI>
  422. <B>Kernel</B>
  423. <P>
  424. We hope to use the Mach message-passing kernel being developed at CMU.
  425. The current distributed version of Mach is not free because it contains
  426. code from BSD of AT&#38;T origin. However, Mach developers say that all
  427. this will be replaced with free code, or at least be moved into user
  428. processes. Mach will be free then. This version of Mach should be
  429. available in a couple of months (as of May 1990). Until this happens,
  430. and we see precisely what is available and on what terms, we can't say
  431. for certain whether we can use it.<P>
  432. We will not use Mach unless we can share it with everyone, and all users
  433. can redistribute it. In particular, if an export control prevents
  434. distribution outside the US, we will not use it.<P>
  435. If we can't use Mach, then we may start developing the GNU kernel with
  436. either MIT's TRIX kernel or Berkeley's Sprite system. TRIX is a remote
  437. procedure call kernel which runs and supports basic Unix compatibility
  438. at about the level of Version 7. It needs a lot of additional features.
  439. Sprite is at about the same architectural level as BSD Unix, but has a
  440. fancy distributed file system and process migration.<P>
  441. <LI>
  442. <B>GNU Debugger</B>
  443. <P>
  444. The GNU source-level C debugger, GDB, is now being distributed along
  445. with the GNU C Compiler as GDB Version 3.5. Version 2.8, that used to
  446. be distributed on the Emacs tape, is now obsolete, and has been replaced
  447. by Version 3.5.<P>
  448. We have also started work on GDB Version 4. We have added watchpoints,
  449. remote cross-debugging, and a host of minor features. We plan to add
  450. over-the-ethernet debugging before the initial release of Version
  451. 4.<P>
  452. <LI>
  453. <B>C Compiler</B>
  454. <P>
  455. The GNU C compiler (GCC) Version 1 is now quite reliable. It supports
  456. ANSI standard C. NeXT builds its entire system, including its port of
  457. the Mach kernel and NFS, with GCC. We have also been told that GCC
  458. successfully compiled a System V.3 kernel. GCC has compiled almost all
  459. of the BSD source tree.<P>
  460. GCC performs automatic register allocation, invariant code motion from
  461. loops, common subexpression elimination, induction variable
  462. optimizations, constant propagation and copy propagation, delaying
  463. popping of function call arguments, tail recursion elimination, and many
  464. local optimizations that are automatically deduced from the machine
  465. description.<P>
  466. Supported CPUs include the 680x0, Vax, 32x32, 80386, 80860, Sparc (Sun
  467. 4), SPUR, Convex, MIPS, Tahoe, Pyramid, and Alliant.<P>
  468. We are trying to stabilize GCC Version 1 while incorporating new
  469. improvements into Version 2. Version 2 now has support for nested
  470. functions, a certain amount of CSE between basic blocks, and a new
  471. feature for classifying instructions--which can be used to choose
  472. between long and short branches or to provide raw data for instruction
  473. scheduling. Instruction scheduling and perhaps global CSE will be added
  474. by the time Version 2 is finished. More general calling conventions are
  475. supported.<P>
  476. Version 2 supports both C++ and Objective C on the same basis as C
  477. itself: the name of the source file selects the language. Michael
  478. Tiemann of Cygnus Support has written the C++ front end for GCC (which
  479. is available in Version 1 as G++). The front end for Objective C has
  480. been donated by NeXT. It will support the Motorola 88000, AMD 29000,
  481. IBM RT, and TRON. Ports for the IBM 370, the 3b2, the Ncube, a Gould
  482. machine (we don't know which one), and the HP Spectrum may be
  483. written.<P>
  484. Front ends for Modula, Fortran and Pascal are being developed by
  485. volunteers. There are rumors about various other languages. So far, no
  486. one has volunteered to write Ada or Cobol.<P>
  487. <LI>
  488. <B>C Library</B>
  489. <P>
  490. Roland McGrath and others continue to work on the C Library. The C
  491. library currently contains all of the ANSI C and POSIX.1 functions, and
  492. work is in progress on POSIX.2 and Unix features. This means that the
  493. library will have not only all of ANSI, POSIX 1003.1, and POSIX 1003.2,
  494. but almost everything found in BSD and System V.<P>
  495. The GNU regular-expression functions (<CODE>regex</CODE>) are now mostly
  496. conformant to the POSIX.2 standard.<P>
  497. <LI>
  498. <B>Ghostscript</B>
  499. <P>
  500. We are distributing Ghostscript on tape. This program provides nearly
  501. all the facilities of a Postscript interpreter.<P>
  502. Ghostscript release 1.4 is now available. Staff members Karl Berry and
  503. Kathy Hargreaves are working on preparing a new release of Ghostscript,
  504. together with Peter Deutsch, the original author of the program. Kathy
  505. and Karl are also working on producing free PostScript font
  506. files.<P>
  507. Highlights of the new release include drivers for HP's Deskjet and
  508. Laserjet as well as the Epson LX-800 (all in low density mode).
  509. Ghostscript may be built with multiple drivers (e.g. an X Window driver
  510. and a printer driver), and you can switch between them
  511. dynamically.<P>
  512. The new release also includes about 20 scalable fonts algorithmically
  513. derived from the BDF fonts in the X11 distribution. These include
  514. Charter, Courier, Helvetica, New Century Schoolbook, Symbol, and Times
  515. fonts. All but the Symbol are provided in different variations.<P>
  516. Right now, Ghostscript will accept commands in PostScript and execute
  517. them by drawing on an X Window or writing a file that can be transferred
  518. directly to a printer. It also includes a C-callable graphics library
  519. (for client programs that don't want to deal with the PostScript
  520. Language), and supports IBM PCs and compatibles with EGA graphics as
  521. well (but don't ask us about this; we don't use PCs and don't have time
  522. to learn anything about them).<P>
  523. Ghostscript needs enhancements: to serve as a previewer for multi-page
  524. files; to serve other X clients by drawing on their windows; to be
  525. improved both in its performance and visual quality; and more fonts.
  526. Any suggestions for enhancements are welcome.<P>
  527. <LI>
  528. <B>GNU Finger</B>
  529. <P>
  530. Brian Fox has released the new GNU Finger program. Finger is a
  531. daemon-based replacement for (or supplement to) BSD <CODE>finger</CODE>. Our
  532. finger now handles the newer paradigm of each user having his/her own
  533. small Unix host (workstation). GNU finger has a per site server that
  534. will poll all of the machines at a site. Thus queries can now be site
  535. wide rather than host specific. For example, fingering
  536. <B>bfox@pogo.ai.mit.edu</B> with our finger would tell you if he was
  537. logged in and what host he is using. If he isn't logged in, it will
  538. tell you what host he was last using.<P>
  539. Our finger also does faces! If a site has face bitmaps online (and is
  540. running GNU Finger, of course) you can get the user's face in a X Window
  541. on your display.<P>
  542. <LI>
  543. <B>Oleo</B>
  544. <P>
  545. Jay Fenlason is writing a spreadsheet named Oleo (which is better for
  546. you than the more expensive spreadsheet). Oleo is in alpha test right
  547. now; we do not know when it will be available. Jay says that "really
  548. brave" people can contact him about being alpha testers.<P>
  549. Oleo currently reads and writes SC and Multiplan SYLK files, but
  550. teaching it new formats is fairly simple. It has a full set of
  551. expressions as well as mathematical, financial, and string functions.
  552. Keys may all be rebound and Oleo also has primitive macro
  553. support.<P>
  554. Oleo uses the <CODE>curses</CODE> library and an X11 interface is planned.
  555. Right now it runs on BSD Unix machines as well as IBM PC's and
  556. compatibles.<P>
  557. <LI>
  558. <B>groff</B>
  559. <P>
  560. James Clark is writing <CODE>groff</CODE>, an implementation in C++ of the
  561. traditional Unix document formatting tools. So far <CODE>troff</CODE>,
  562. <CODE>pic</CODE>, <CODE>tbl</CODE>, <CODE>eqn</CODE>, <CODE>man</CODE> macros, and a PostScript
  563. driver have been written. A version of the Berkeley <CODE>me</CODE> macros
  564. will be included. He is currently implementing a driver which produces
  565. TeX <CODE>.dvi</CODE> format and a driver for typewriter-like devices.
  566. Useful additions would be <CODE>mm</CODE> and <CODE>ms</CODE> macros, <CODE>grap</CODE>,
  567. and <CODE>refer</CODE>.<P>
  568. <LI>
  569. <B>GNU Mailer</B>
  570. <P>
  571. Development of Smail is coming to an end. We are satisfied with the
  572. program's current features, except for the queueing system. We hope we
  573. can replace Smail's queueing system with the queueing system found in
  574. Zmailer. Otherwise a new one will have to be written.<P>
  575. <LI>
  576. <B>File Manipulation Utilities</B>
  577. <P>
  578. We have added a collection of utilities for file manipulation to the
  579. Pre-Release tape. The collection includes <CODE>ls</CODE>, <CODE>mv</CODE>,
  580. <CODE>cp</CODE>, <CODE>cat</CODE>, <CODE>rm</CODE>, <CODE>du</CODE>, <CODE>head</CODE>, <CODE>tail</CODE>,
  581. <CODE>cmp</CODE>, <CODE>chmod</CODE>, <CODE>mkdir</CODE>, and <CODE>ln</CODE>. These tools are
  582. either fully POSIX compliant or being worked on to become so. <CODE>cp</CODE>
  583. now has options to preserve the last-modification timestamp on copies,
  584. thus replacing some uses of <CODE>tar</CODE> or <CODE>cpio</CODE>.<P>
  585. <LI>
  586. <B>Smalltalk</B>
  587. <P>
  588. Our Smalltalk system will be available in tape form when we release our
  589. "Experimental" tape in November. It is currently available via
  590. <CODE>ftp</CODE> on <CODE>prep.ai.mit.edu</CODE>. The current version is 1.1, with
  591. Version 1.2 expected to be out soon. Thanks to Steve Byrne who wrote
  592. our Smalltalk based on the <CITE>blue book</CITE> definition of the
  593. language.</UL>
  594. <P>
  595. <H1><A NAME="SEC12" HREF="bull9_toc.html#SEC12">GNU Wish List</A></H1>
  596. <P>
  597. Wishes for this issue are for:<P>
  598. <UL>
  599. <LI>
  600. Someone skilled in compiler maintenance who could take over GCC
  601. maintenance for RMS. This would probably be a full-time job.<P>
  602. <LI>
  603. A Sun with a SCSI port to be donated or loaned so we can make
  604. distribution tapes. We also need machines to be donated or loaned for
  605. use by FSF programmers and documentation people who are not located near
  606. our offices in Cambridge.<P>
  607. <LI>
  608. Professors who might be interested in sponsoring or hosting research
  609. assistants to do GNU development, with full or partial FSF support.
  610. Several schools have done this and we welcome others to join in.<P>
  611. <LI>
  612. Volunteers to help write utilities and documentation. Send mail to
  613. <CODE>gnu@prep.ai.mit.edu</CODE> for the task list and coding
  614. standards.<P>
  615. <LI>
  616. Speech and character recognition software (if the devices aren't too
  617. weird), with the device drivers (if possible). This would help the
  618. productivity of at least one partially disabled programmer we
  619. know.<P>
  620. <LI>
  621. Grammar checking software for English and other natural
  622. languages.<P>
  623. <LI>
  624. Copies of newspaper and journal articles mentioning the GNU Project or
  625. GNU software. Send these to the address on the front cover, or send a
  626. citation to <CODE>gnu@prep.ai.mit.edu</CODE>.<P>
  627. <LI>
  628. Money, as always. Please remember, donations are tax-deductible. With
  629. the latest donations, we have been able to expand our staff again. With
  630. the increased staff we have an even greater need for donations.<P>
  631. One way to give us a small amount of money is to order a distribution
  632. tape or two. This may not count as a donation for tax purposes, but it
  633. can qualify as a business expense.<P>
  634. </UL>
  635. <P>
  636. <H1><A NAME="SEC13" HREF="bull9_toc.html#SEC13">GNU Documentation</A></H1>
  637. <P>
  638. GNU is dedicated to having quality, easy-to-use, on-line and printed
  639. documentation. GNU manuals are intended to explain the underlying
  640. concepts, describe how to use all the features of each program, and give
  641. examples of command use.<P>
  642. GNU documentation is distributed as Texinfo source files. Texinfo
  643. source yields both a typeset hardcopy and on-line presentations,
  644. accessed by a menu-driven system.<P>
  645. The following manuals, provided with our software, are also available in
  646. hardcopy; see the order form on the inside back cover.<P>
  647. The <B>Emacs Manual</B> describes the use of GNU Emacs. It also explains
  648. advanced features, such as outline mode and regular expression search.
  649. The manual tells how to use special modes for programming in languages
  650. such as C and Lisp, how to use the tags utility, and how to compile and
  651. correct code. It also describes how to make your own keybindings and
  652. other elementary customizations.<P>
  653. The <B>Emacs Lisp Reference Manual</B> covers the GNU Emacs Lisp
  654. programming language in great depth. It goes into data types, control
  655. structures, functions, macros, byte compilation, keymaps, windows,
  656. markers, searching and matching, modes, syntax tables, operating system
  657. interface, etc.<P>
  658. The <B>Texinfo Manual</B> describes how to write documents in Texinfo
  659. source code. It explains the markup language used to create both an
  660. Info file and a printed document from the same source file. This tells
  661. you how to make tables, lists, chapters, nodes, indices, and cross
  662. references. It also describes how to use Texinfo mode in GNU Emacs and
  663. catch mistakes.<P>
  664. The <B>Termcap Manual</B> is often described as "Twice as much as you ever
  665. wanted to know about Termcap." It describes the format of the Termcap
  666. database, the definitions of terminal capabilities, and the process of
  667. interrogating a terminal description. This manual is primarily for
  668. programmers.<P>
  669. The <B>Bison Manual</B> covers writing grammar descriptions that can be
  670. converted into C coded parsers. This manual assumes no prior
  671. knowledge of parser generators. It describes the concepts and then
  672. provides a series of increasingly complex examples before
  673. describing what happens in considerable detail.<P>
  674. The <B>GAWK Manual</B> describes how to use the GNU implementation of AWK.
  675. It is written for someone who has never used AWK, and describes all the
  676. features of this powerful string manipulating language.<P>
  677. The <B>Make Manual</B> describes the GNU Make utility, a program used to
  678. rebuild parts of other programs when and as needed. It covers makefile
  679. writing, which specifies how a program is to be compiled and what each
  680. part of the program depends on.<P>
  681. The <B>GDB Manual</B> explains how to use the GNU Debugger. It describes
  682. running your program under debugger control, how to examine and alter
  683. data as well as modify the flow of control within the program, and how
  684. to use GDB through GNU Emacs, with auto-display of source lines.<P>
  685. <H1><A NAME="SEC14" HREF="bull9_toc.html#SEC14">GNU Software Available Now</A></H1>
  686. <P>
  687. We offer Unix software source distribution tapes, plus VMS tapes for GNU
  688. Emacs and GNU C that include sources and VMS executables.<P>
  689. The first Unix tape (called the "Release" or "Emacs" tape) contains
  690. GNU Emacs as well as various other well-tested programs that we consider
  691. reliable. The second Unix tape (called the "Pre-Release" or
  692. "Compiler" tape) contains the GNU C compiler, related utilities, and
  693. other new programs that are less thoroughly tested. The third and
  694. fourth Unix tapes (called the "X11" tapes) contain the X11
  695. distribution from the MIT X Consortium.<P>
  696. The GNU C compiler and various related programs are on a tape that we
  697. have called our "Beta Test" tape in the past. However, this software
  698. is becoming more stable; to reflect this change, we are renaming the
  699. tape the "Pre-Release" tape. (The tape also contains Ghostscript,
  700. which is not stable; for the moment, this is the best place to put
  701. it.)<P>
  702. Sometime in the Fall, probably in early November, we will introduce a
  703. new beta test tape of "experimental" software. We will put new major,
  704. test releases of existing more-or-less stable programs such as GCC,
  705. Emacs, and GDB on this tape when they appear, as well as new programs
  706. such as Smalltalk and the C library. The contents of the
  707. "Experimental" tape will fluctuate because versions will move to the
  708. other tapes when they become stable. We are calling this the
  709. "Experimental" tape to prevent confusion with the older Beta
  710. tape.<P>
  711. We will put Ghostscript on the "Experimental" tape when it appears.
  712. But as a convenience, we will continue to include it on the
  713. "Pre-Release" tape until the current order form expires in January
  714. 1991, even though this action is somewhat inconsistent with the tape
  715. naming conventions.<P>
  716. Please do not order an "Experimental" tape until at least November,
  717. unless you see an announcement sooner than that on the net--we have put
  718. nothing on this tape as yet!<P>
  719. See the order form on the inside back cover for details about media,
  720. etc. Note that the contents of the 1600bpi 9-track tapes and the QIC-24
  721. DC300XLP 1/4 inch cartridge tapes for UNIX systems are the same. It is
  722. only the media that are different.<P>
  723. <H3><A NAME="SEC15" HREF="bull9_toc.html#SEC15">Contents of the Emacs Release Tape</A></H3>
  724. <P>
  725. The software on this release tape is considered fairly stable, but as
  726. always, we welcome your bug reports.<P>
  727. <UL>
  728. <LI>
  729. <B>GNU Emacs</B>
  730. <P>
  731. In 1975, Richard Stallman developed the first Emacs, an extensible,
  732. customizable real-time display editor. GNU Emacs is his second
  733. implementation of Emacs. It's the first Emacs available on Unix systems
  734. that offers true Lisp--smoothly integrated into the editor--for
  735. writing extensions. It also provides a special interface to MIT's free
  736. X window system. The current version of Emacs is 18.55.<P>
  737. GNU Emacs has been in widespread use since 1985 and often displaces
  738. proprietary implementations of Emacs because of its greater reliability
  739. as well as its additional features and easier extensibility. DEC,
  740. Berkeley, and NeXT are all distributing Emacs with their systems. When
  741. Isaac Salzman set out to review various versions of Emacs, only one
  742. company wanted its product to be compared with GNU Emacs. In his
  743. review, which appeared in the July, 1989 issue of <I>Unix Review</I>,
  744. Salzman concluded, "When it comes to Emacs, GNU is the way to
  745. go."<P>
  746. pGNU Emacs (as of Version 18.55) runs on many Unix systems: Alliant,
  747. Altos 3068, Amdahl (UTS), Apollo, AT&#38;T (3B machines &#38; 7300 PC), CCI 5/32
  748. &#38; 6/32, Celerity, Convex, Digital (DECstation 3100; Vax running BSD or
  749. System V), Motorola Delta (running System V/68 release 3), Dual, Elxsi
  750. 6400, Encore (DPC, APC, &#38; XPC), Gould, HP (9000 series 200, 300 or 800
  751. (Spectrum) but not series 500), HLH Orion 1/05, IBM (RT/PC running 4.2 &#38;
  752. AIX; PS2 running AIX), Integrated Solutions (Optimum V with 68020 &#38;
  753. VMEbus), Intel 80386 (BSD, System V, &#38; Xenix; not MS-DOS), Iris (2500,
  754. 2500 Turbo, &#38; 4D), LMI (Nu), Masscomp, Megatest, MIPS, NCR (Tower 32),
  755. Nixdorf Targon 31, Plexus, Prime, Pyramid, Sequent (Balance &#38; Symmetry),
  756. SONY News, Stride (system release 2), Sun (1, 2, 3, 4, SparcStation, &#38;
  757. 386i), Tahoe, Tektronix (NS32000 &#38; 4300), Stardent 1500 or 3000, Titan
  758. P2 or P3, Pmax, Texas Instruments (Nu), &#38; Whitechapel (MG1).<P>
  759. GNU Emacs is described by the <CITE>GNU Emacs Manual</CITE>, which comes with
  760. the software in Texinfo form. See "GNU Documentation" above. Also,
  761. since GDB is the only debugger that can debug Emacs without losing its
  762. mind, it is included on this tape as well as the Pre-Release
  763. Tape.<P>
  764. <LI>
  765. <B>GNU Emacs Lisp Reference Manual</B>
  766. <P>
  767. We now include the Texinfo source to the <CITE>GNU Emacs Lisp Reference
  768. Manual</CITE> with Emacs. The manual describes the GNU Emacs Lisp programming
  769. language in detail and is for anyone who is interested in writing
  770. programs in GNU Emacs Lisp. See "GNUs Flashes" and "GNU
  771. Documentation" in this bulletin for more information.<P>
  772. <LI>
  773. <B>Bison</B>
  774. <P>
  775. Bison is an upwardly compatible replacement for the parser generator
  776. Yacc, with additional features. It has been in use for several years.
  777. Bison is used for compiling GNU C, so it is included on the GNU
  778. Pre-Release tape as well. The <CITE>Bison Manual</CITE> comes with the
  779. software in Texinfo form (see "GNU Documentation" above).<P>
  780. <LI>
  781. <B>X Window System, V10R4</B>
  782. <P>
  783. We are no longer including a copy of X10 on our distribution tapes. It
  784. is no longer supported by MIT, so distributing it does not make sense.
  785. X Version 11 (currently release 4) is now pretty stable and available
  786. from us on two separate tapes. See "Contents of the X11
  787. Tapes."<P>
  788. <LI>
  789. <B>MIT Scheme</B>
  790. <P>
  791. Scheme is a simplified, lexically scoped dialect of Lisp. It was
  792. designed at MIT and other universities to teach students programming and
  793. to research new parallel programming constructs and compilation
  794. techniques. MIT Scheme is written in C and runs on many Unix systems.
  795. It now conforms to the {\sl Revised\/$^3$ Report On The Algorithmic
  796. Language Scheme\/} (MIT AI Lab Memo 848a), for which \TeX\ source is
  797. included in the distribution. Another good source of documentation for
  798. Scheme is {\sl Structure and Interpretation of Computer Programs}, by
  799. Harold Abelson and Gerald J. Sussman with Julie Sussman, the MIT Press
  800. \&#38; McGraw-Hill Book Company, 1985.
  801. <P>
  802. <LI>
  803. <B>Yale T</B>
  804. <P>
  805. A variant of Scheme developed at Yale University, T is intended for
  806. production use in program development. T contains a native-code
  807. optimizing compiler that produces code that runs at speeds comparable to
  808. the speeds of programs written in conventional languages. It runs on
  809. BSD Vaxes, 680x0 systems, SPARC workstations, MIPS R2000 workstations
  810. (including the Decstation 3100 PMAX), and NS32000 machines (including
  811. the Encore Multimax). T is written in itself and cannot be bootstrapped
  812. without a binary (included), but it is great if you can use it. Some
  813. documentation is included.<P>
  814. <LI>
  815. <B><CODE>texi2roff</CODE></B>
  816. <P>
  817. <CODE>texi2roff</CODE>, written by Beverly Erlebacher, translates GNU Texinfo
  818. files into a format that can be printed by the Unix [nt]roff programs
  819. utilizing the mm, ms or me macro packages. It is included on all UNIX
  820. tapes so people who don't have a copy of TeX can print out GNU
  821. documentation.<P>
  822. <LI>
  823. <B>GNU Chess and NetHack</B>
  824. <P>
  825. GNU Chess is a chess program, now in its second major version. The
  826. first was written by Stuart Cracraft. The second was written and
  827. donated by John Stanback. If a successor is found that is
  828. significantly stronger, it could become the new GNU Chess. GNU Chess
  829. has text-only and X display interfaces.<P>
  830. NetHack is a display--oriented adventure game similar to Rogue.<P>
  831. </UL>
  832. <P>
  833. <H3><A NAME="SEC16" HREF="bull9_toc.html#SEC16">Contents of the Pre-Release Tape</A></H3>
  834. <P>
  835. The programs on this tape are becoming almost stable. The exception is
  836. Ghostscript, but which we are carrying on this tape as a convenience
  837. until January 1991, when we will distribute it only on the
  838. "Experimental" tape. As always, we solicit your comments and bug
  839. reports. This tape is also known as the Compiler tape, and used to be
  840. known as the "Beta" tape.<P>
  841. <UL>
  842. <LI>
  843. <B>GNU CC</B>
  844. <P>
  845. The GNU C compiler is a fairly portable optimizing compiler. It
  846. generates good code for the 32000, 680x0 (optionally with 68881/2),
  847. 80386, 860, 88000, Alliant, Convex, Tahoe, and Vax CPUs, and for these
  848. RISC CPUs: Pyramid, SPARC, and SPUR. The MIPS RISC CPU is also
  849. supported. Machines using these CPUs include 386 running AIX, Alliant
  850. FX/8, Altos 3068, Apollo 68000/68020 running Aegis, AT&#38;T 3B1, Convex C1
  851. and C2, DECstation 3100, DEC VAX, Encore MultiMax (NS32000), Genix
  852. NS32000, Harris HCX-7 and HCX-9, HP-UX 68000/68020, HP running BSD, IBM
  853. PS/2 running AIX, Intel 386, Iris MIPS machine, ISI 68000/68020, MIPS,
  854. NeXT, Pyramid, Sequent Balance (NS32000), Sequent Symmetry (i386), SONY
  855. News, Sun 2, Sun 3 (optionally with FPA), Sun 4, SparcStation, and
  856. Sun386i. The current version is 1.37. It supports full ANSI C. Please
  857. refer to the "GNU Project Status Report" for more detail on
  858. GCC.<P>
  859. Included with the compiler are Bison (also on the Emacs release tape),
  860. and the perfect hash-table generating utility (Gperf), plus the Texinfo
  861. source of the <CITE>GCC Manual</CITE>. This manual describes how to run and
  862. install the GNU C compiler, and how to port it to new processors. It
  863. describes new features and incompatibilities of the compiler, but people
  864. not familiar with C will also need a good book on C.<P>
  865. <LI>
  866. <B>Assembler and Object File Utilities</B>
  867. <P>
  868. The GNU assembler (GAS) is a fairly portable, one pass assembler that is
  869. almost twice as fast as Unix <CODE>as</CODE>. It is now at Version 1.35 and
  870. works for 32x32, 680x0, 80386, Sparc (Sun 4), and Vax.<P>
  871. We have free versions of <CODE>ar</CODE>, <CODE>ld</CODE>, <CODE>nm</CODE>, <CODE>size</CODE>,
  872. <CODE>gprof</CODE>, <CODE>strip</CODE>, and <CODE>ranlib</CODE>. The GNU linker <CODE>ld</CODE>
  873. runs significantly faster than the BSD version. Our <CODE>ld</CODE> is the
  874. only one that will give you source-line numbered error messages for
  875. multiply-defined symbols and undefined references.<P>
  876. <LI>
  877. <B>COFF Support</B>
  878. <P>
  879. It is possible to run the entire suite of GNU software tools on System
  880. V, replacing COFF entirely. The GNU tools can operate on BSD object
  881. files with a COFF header the System V kernel will accept.
  882. <CODE>robotussin</CODE> is supplied for converting standard libraries to this
  883. format.<P>
  884. <LI>
  885. <B><CODE>make</CODE></B>
  886. <P>
  887. GNU <CODE>make</CODE> includes almost all the features from the BSD, System V,
  888. and POSIX versions of make, as well many of our own extensions. These
  889. extensions include parallelism, conditional execution, and text
  890. manipulation. Version 3 of GNU make is fairly stable and we do not
  891. anticipate a Version 3 release after 3.59. Work on Version 4--which
  892. will include many functional improvements--will begin sometime this
  893. summer. Texinfo source for the GNU make manual is provided; see "GNU
  894. Documentation" above.<P>
  895. <LI>
  896. <B>Debugger</B>
  897. <P>
  898. Version 3.<CODE>*</CODE> of GDB, the GNU debugger, runs under BSD 4.2 and 4.3
  899. on Vaxes and Suns (2, 3, and 4), Convex, HP 9000/300's under BSD, HP
  900. 9000/320's under HPUX, System V 386 machines (with either GNU or native
  901. object file format), ISI Optimum V, Merlin under Utek 2.1, SONY News,
  902. Gould NPL and PN machines, Pyramid, Sequent Symmetry (a 386 based
  903. machine), Altos, and Encores under Umax 4.2.<P>
  904. GDB features incremental reading of symbol tables (for fast startup and
  905. less memory use), command-line editing, the ability to call functions in
  906. the program being debugged, a value history, and user-defined commands.
  907. It can be used to debug C, C<CODE>++</CODE>, and FORTRAN programs.<P>
  908. GDB also provides for remote debugging over a serial line. Remote
  909. debugging is the most convenient way to develop software for systems
  910. which are too small to run a debugger; it allows you to have the
  911. features of GDB at your disposal even on such systems.<P>
  912. <LI>
  913. <B>BASH</B>
  914. <P>
  915. The GNU Shell, BASH (for Bourne Again SHell), provides compatibility
  916. with the Unix <CODE>sh</CODE> and provides many extensions found in <CODE>csh</CODE>
  917. and <CODE>ksh</CODE>. It has job control, <CODE>csh</CODE>-style command history,
  918. and command-line editing (with Emacs and vi modes built-in and the
  919. ability to rebind keys).<P>
  920. <LI>
  921. <B>GAWK, FLEX, and <CODE>tar</CODE></B>
  922. <P>
  923. GAWK is GNU's version of the Unix AWK utility; it comes with a Texinfo
  924. manual (see "GNU Documentation" above). FLEX is a mostly-compatible
  925. replacement for the Unix <CODE>lex</CODE> scanner generator written by Vern
  926. Paxson of the Lawrence Berkeley Laboratory. FLEX generates far more
  927. efficient scanners than <CODE>lex</CODE> does. GNU <CODE>tar</CODE> includes
  928. multivolume support, the ability to archive sparse files, automatic
  929. compression and decompression of archives, remote archives, and special
  930. features to allow <CODE>tar</CODE> to be used for incremental and full backups
  931. of file systems.<P>
  932. <LI>
  933. <B>Freed Files from the U.C. Berkeley 4.3-tahoe Release</B>
  934. <P>
  935. These files have been declared by Berkeley to be free of AT&#38;T code, and
  936. may be freely redistributed. They include complete sources for some
  937. utility programs, games, and library routines; and partial sources for
  938. many others.<P>
  939. <LI>
  940. <B>RCS and CVS</B>
  941. <P>
  942. The Revision Control System is used for version control and management
  943. of large software projects. This is the latest version (4.0).<P>
  944. CVS, the Concurrent Version System written by Brian Berliner, manages
  945. software revision and release control in a multi-developer,
  946. multi-directory, multi-group environment. It is designed to work on top
  947. of RCS Version 4, but will parse older RCS formats with the loss of
  948. CVS's fancier features. For further details, see Berliner, Brian,
  949. <CITE>CVS-II: Parallelizing Software Development,</CITE> Proceedings of the
  950. Winter 1990 USENIX Association Conference.<P>
  951. <LI>
  952. <B><CODE>diff</CODE> and <CODE>grep</CODE></B>
  953. <P>
  954. These programs are GNU's versions of the Unix programs of the same name.
  955. They are much faster than their Unix counterparts.<P>
  956. <LI>
  957. <B>Ghostscript and <CODE>gnuplot</CODE></B>
  958. <P>
  959. Ghostscript is GNU's graphics language that is almost fully compatible
  960. with PostScript. For more information on Ghostscript, please refer to
  961. the section on Ghostscript in the "GNU Project Status Report."<P>
  962. <CODE>gnuplot</CODE> is an interactive program for plotting mathematical
  963. expressions and data. Oddly enough, the program was neither done for
  964. nor named for the GNU Project--the name is a coincidence.<P>
  965. <LI>
  966. <B><CODE>g++</CODE>, <CODE>libg++</CODE>, and NIH Class Library</B>
  967. <P>
  968. G<CODE>++</CODE> is a set of changes for GCC that compiles C<CODE>++</CODE>, the
  969. well-known object-oriented language. This was the first compiler to
  970. compile C<CODE>++</CODE> directly instead of preprocessing it into C, with
  971. great benefits for debugging and efficiency. G<CODE>++</CODE> also was first
  972. with multiple inheritance and other new features later released by AT&#38;T
  973. in <CODE>cfront 2.0</CODE>. Since G<CODE>++</CODE> depends on GCC, it must be used
  974. with the correspondingly numbered version of GCC. GDB Version
  975. 3.<CODE>*</CODE> includes support for debugging C<CODE>++</CODE> code, which merges
  976. in the functionality of the old program GDB<CODE>+</CODE>.<P>
  977. <CODE>libg++</CODE> (the GNU C<CODE>++</CODE> library) is an extensive and
  978. documented collection of C<CODE>++</CODE> classes and support tools for use
  979. with G<CODE>++</CODE>.<P>
  980. The NIH Class Library (formerly known as OOPS (Object-Oriented Program
  981. Support)) is a portable collection of classes similar to those in
  982. Smalltalk-80 that has been developed by Keith Gorlen of NIH, using the
  983. C<CODE>++</CODE> programming language.<P>
  984. Note that Interviews has been dropped from this tape since it appears on
  985. the "optional" X tape (See "Contents of the X11 Tapes"
  986. below).<P>
  987. <LI>
  988. <B>File Utilities and Miscellaneous</B>
  989. <P>
  990. The file utilities, which include the programs listed in the "GNU
  991. Status Report," are now included here. We also include
  992. <CODE>compress</CODE>, <CODE>perl</CODE> (Version 3.0), <CODE>c-perf</CODE> (Version 2.0),
  993. <CODE>f2c</CODE> (a FORTRAN to C translator), and GnuGo (the game of Go
  994. (Wei-Chi)) on this tape.<P>
  995. </UL>
  996. <P>
  997. <H3><A NAME="SEC17" HREF="bull9_toc.html#SEC17">Contents of the X11 Tapes</A></H3>
  998. <P>
  999. The two X11 tapes contain Version 11, Release 4 of the MIT X window
  1000. system. X11 is more powerful than, but incompatible with, the
  1001. no-longer-supported Version 10.<P>
  1002. The first FSF tape contains the contents of both tape one and tape two
  1003. from the MIT X Consortium: the core software and documentation, and the
  1004. contributed clients. FSF refers to its first tape as the `required' X
  1005. tape since it is necessary for running X or GNU Emacs under X. (The
  1006. Consortium refers to its first two tapes as the `required/recommended'
  1007. tapes.)<P>
  1008. The second, `optional' FSF tape contains the contents of tapes three and
  1009. four from the MIT X Consortium: contributed libraries and other
  1010. toolkits, the Andrew software, games, etc. (The Consortium refers to
  1011. its last two tapes as `optional' tapes.)<P>
  1012. <H3><A NAME="SEC18" HREF="bull9_toc.html#SEC18">VMS Emacs and Compiler Tapes</A></H3>
  1013. <P>
  1014. We offer a VMS tape of the GNU Emacs editor, and a separate VMS tape
  1015. containing the GNU C compiler. The VMS compiler tape also contains
  1016. Bison (needed to compile GCC), GAS (needed to assemble GCC's output),
  1017. and some library and include files. Both VMS tapes include executables
  1018. that you can bootstrap from, because the DEC VMS C compiler has bugs and
  1019. thus cannot compile GNU C.<P>
  1020. Please don't ask us to devote effort to additional VMS support, because
  1021. it is peripheral to the GNU Project.<P>
  1022. <H1><A NAME="SEC19" HREF="bull9_toc.html#SEC19">How to Get GNU Software</A></H1>
  1023. <P>
  1024. All the software and publications from the Free Software Foundation are
  1025. distributed with permission to copy and redistribute. The easiest way
  1026. to get GNU software is to copy it from someone else who has it.<P>
  1027. If you have access to the Internet, you can get the latest software from
  1028. the host <CODE>prep.ai.mit.edu</CODE>. For more information, read the
  1029. file <TT>`/u/emacs/GETTING.GNU.SOFTWARE'</TT> on that host. Please note
  1030. that the Internet address of <CODE>prep</CODE> is
  1031. <CODE>18.71.0.38</CODE>.<P>
  1032. If you cannot get the software from a friend or over the net, or if you
  1033. would like to contribute some funds to our efforts and receive the
  1034. latest versions, the Free Software Foundation distributes tapes for a
  1035. copying and distribution fee. See the order form on the inside back
  1036. cover.<P>
  1037. There are also third party groups that distribute our software: they do
  1038. not work with us, but have our software in other forms. For your
  1039. convenience, some of them are listed below. Please note that the Free
  1040. Software Foundation is <I>not</I> affiliated with them in any way, and is
  1041. not responsible for either the currency of their versions or the
  1042. swiftness of their responses.<P>
  1043. These Internet sites provide GNU software via anonymous
  1044. <CODE>ftp</CODE>:<P>
  1045. <PRE>
  1046. scam.berkeley.edu, itstd.sri.com, wuarchive.wustl.edu,
  1047. wsmr-simtel20.army.mil (under <TT>`PD:&#60;UNIX.GNU&#62;'</TT>), bu.edu,
  1048. louie.udel.edu, nic.nyser.net, ftp.cs.titech.ac.jp,
  1049. funic.funet.fi, sunic.sunet.se, freja.diku.dk,
  1050. gatekeeper.dec.com, mango.miami.edu (VMS G++),
  1051. cc.utah.edu (VMS GNU Emacs), and uunet.uu.net.
  1052. </PRE>
  1053. <P>
  1054. Those on the SPAN network can ask <TT>rdss::corbet</TT>.<P>
  1055. Information on how to obtain some GNU programs using UUCP is available
  1056. via electronic mail from the following people. Ohio State also posts
  1057. their UUCP instructions regularly to newsgroup <CODE>comp.sources.d</CODE> on
  1058. USENET.<P>
  1059. <PRE>
  1060. hao!scicom!qetzal!upba!ugn!nepa!denny, acornrc!bob,
  1061. hqda-ai!merlin, uunet!hutch!barber, sun!nosun!illian!darylm,
  1062. oli-stl!root, bigtex!james, postmaster@uunet.uu.net, and
  1063. karl@tut.cis.ohio-state.edu (or <CODE>osu-cis!karl)</CODE>.
  1064. </PRE>
  1065. <P>
  1066. <H3><A NAME="SEC20" HREF="bull9_toc.html#SEC20">Freemacs, an Extensible Editor for MS-DOS</A></H3>
  1067. <P>
  1068. Freemacs, a copylefted MS-DOS editor, is one of the few editors for
  1069. small machines with a full extension language. It is the only such
  1070. editor that tries to be compatible with GNU Emacs. For more information
  1071. contact: <CODE>nelson@clutx.clarkson.edu</CODE>, or: Russell Nelson, 11
  1072. Grant St., Potsdam, NY, 13676. $15 sent to that address will get you a
  1073. copy. It is also available for <CODE>ftp</CODE> on
  1074. <CODE>sun.soe.clarkson.edu</CODE>. Note that the Free Software Foundation
  1075. does not distribute Freemacs; please don't ask us about it.<P>
  1076. <H1><A NAME="SEC21" HREF="bull9_toc.html#SEC21">Thank GNUs</A></H1>
  1077. <P>
  1078. Thanks to all those mentioned in GNUs Flashes and the GNU Project Status
  1079. Report.<P>
  1080. Thanks to the <B>Japanese Unix Society</B> for their large gift.<P>
  1081. Thanks to <B>Delta Microsystems</B> who just donated an Exabyte tape
  1082. drive.<P>
  1083. Thanks again to the <B>Open Software Foundation</B> for their continued
  1084. support.<P>
  1085. Thanks to <B>Digital Equipment Corporation</B> for their gift.<P>
  1086. Thanks to <B>Bil Lewis</B>, <B>Dan LaLiberte</B>, and the volunteers
  1087. who worked on the <CITE>Emacs Lisp Reference Manual</CITE>. Also thanks to
  1088. <B>Warren A. Hunt, Jr.</B> and <B>Computational Logic, Inc.</B> for
  1089. their support.<P>
  1090. Thanks to the <B>MIT</B> <B>Artificial</B> <B>Intelligence</B>
  1091. <B>Laboratory</B> &#38; <B>MIT</B> <B>Laboratory</B> <B>for</B>
  1092. <B>Computer</B> <B>Science</B> for their invaluable assistance of many
  1093. kinds.<P>
  1094. Thanks to <B>Chris Welty</B> as well as the <B>Computer</B>
  1095. <B>Science</B> <B>Department</B> at <B>Rensselaer</B>
  1096. <B>Polytechnic</B> <B>Institute</B> for splitting Dave Lawrence's
  1097. salary with FSF and providing him computing facilities.<P>
  1098. Thanks to <B>Prof. Christof Koch</B> of <B>Caltech</B> for his
  1099. support of Brian Fox.<P>
  1100. Thanks to <B>Prof. Paul Hilfinger</B> of the UCB CS Department for
  1101. allowing Roland McGrath to use UCB resources.<P>
  1102. Thanks to the <B>University</B> <B>of</B> <B>Minnesota</B>
  1103. <B>Department</B> <B>of</B> <B>Computer</B> <B>Science</B> for
  1104. allowing Mike Haertel to use their computers.<P>
  1105. Thanks to <B>Cliff Lasser</B> of <B>Thinking Machines, Inc.</B> for
  1106. the help with upgrading to SunOS 4.0.<P>
  1107. Thanks to <B>Village Center Inc</B> and <B>Nikkei Business
  1108. Publishing</B>, both of Japan, for their gifts.<P>
  1109. Thanks to <B>Information Systems</B> and the <B>Whitaker</B>
  1110. <B>College</B> <B>Computing</B> <B>Facility</B> at <B>MIT</B> for
  1111. use of their machines to make our VMS master tapes.<P>
  1112. Thanks go out to all those who have either lent or donated machines,
  1113. including <B>Hewlett-Packard</B> for their donation of six 68030
  1114. workstations, <B>Brewster Kahle</B> of Thinking Machines Corp.
  1115. (TMC) for the Sun 4/110, <B>K. Richard Magill</B> for the AT&#38;T Unix
  1116. PC, <B>Doug Blewett</B> of AT&#38;T Bell Labs for two Convergent
  1117. Miniframes, CMU's <B>Mach Project</B> for the Sun 3/60, <B>Intel
  1118. Corp.</B> for their 386/i860 workstation, <B>NeXT</B> for a NeXT
  1119. workstation, the <B>MIT Media Laboratory</B> for the Hewlett-Packard
  1120. 68020 machine, <B>SONY Corp.</B> and <B>Software Research
  1121. Associates</B>, Inc., both of Tokyo, for three SONY News workstations, and
  1122. the <B>MIT</B> <B>Laboratory</B> <B>of</B> <B>Computer</B>
  1123. <B>Science</B> for the DEC Microvax.<P>
  1124. Thanks to all those who have contributed ports and extensions, as well
  1125. as those who have contributed other source code, documentation, and good
  1126. bug reports. Thanks to those who sent money and offered help. Thanks
  1127. also to those who support us by ordering manuals and distribution
  1128. tapes.<P>
  1129. <HR>
  1130. <P>
  1131. <PRE>
  1132. -------
  1133. | |
  1134. Free Software Foundation, Inc. | stamp |
  1135. 675 Massachusetts Avenue | |
  1136. Cambridge, MA 02139 USA | here |
  1137. | |
  1138. -------
  1139. </PRE>
  1140. <P>
  1141. <HR>
  1142. <P>
  1143. Use rule at top of this page for page 1.