bull3.html 30 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730
  1. <!-- This HTML file has been created by texi2html 1.30
  2. from bull3.texi on 28 January 1995 -->
  3. <TITLE>GNU's Bulletin, vol. 1 no. 3</TITLE>
  4. <H1>GNU's Bulletin, vol. 1 no. 3</H1>
  5. <H1><A NAME="SEC1" HREF="bull3_toc.html#SEC1">Gnu's Bulletin June, 1987</A></H1>
  6. <P>
  7. Gnu's Bulletin is the sporadically published newsletter of the Free
  8. Software Foundation, bringing you news about the GNU project.
  9. <P>
  10. <HR>
  11. <P>
  12. <H1><A NAME="SEC3" HREF="bull3_toc.html#SEC3">Gnu's Who</A></H1>
  13. <P>
  14. The usual people are still working on GNU: <B>Richard Stallman</B>
  15. recently returned from Korea, where he worked at KAIST during the
  16. month of April. He also visited DECUS in Tokyo and spoke there. He
  17. is currently continuing to develop the GNU C compiler. Hackers <B>Len
  18. Tower</B>, <B>Richard Mlynarik</B>, and <B>Paul Rubin</B> are doing various
  19. pieces of volunteer work as their time permits it, and <B>Jay
  20. Fenlason</B> continues to work full time on the GNU assembler and
  21. libraries. At
  22. the distribution end, FSF treasurer <B>Bob Chassell</B> has just finished
  23. coordinating production of another run of GNU Emacs manuals. <B>Jerry
  24. Puzo</B> has been making sure that our correspondence with the outside
  25. world is handled smoothly.
  26. <P>
  27. Some new people have also joined us: <B>Mark D'Agostino</B> is now taking care
  28. of the FSF mail room, filling the tape and manual orders which are coming
  29. in at an ever increasing rate. Mark is an MIT student in Physics and
  30. Electrical Engineering. <B>Peter Deutsch</B>, an old-time hacker from MIT, is
  31. in his spare time writing a PostScript language interpreter for bitmap
  32. screens, for use with GNU under the X window system. His interpreter will
  33. be called "GhostScript" and will hopefully also be able to drive
  34. printers. Peter is well known for his work on Lisp and Smalltalk, and
  35. continues to do Smalltalk development as Chief Scientist at ParcPlace
  36. Systems, a spinoff of Xerox PARC. <B>Velu Sinha</B> wrote the GNU shell,
  37. which will be released for testing soon. <B>Rayan Zachariasen</B>, whose name
  38. I hope I have not misspelled, is writing a mailer. Finally, <B>Kathy
  39. Hargreaves</B> and <B>Karl Berry</B> transcribed Richard Stallman's Microwave Day
  40. lecture on how the GNU C compiler works; we hope to publish an edited
  41. version of the transcript soon. Kathy and Karl are both studying digital
  42. typography in the Brown University CS department. They plan later to
  43. design some type fonts for use with GhostScript. They also designed the
  44. new FSF order form that appears at the end of this bulletin.
  45. <P>
  46. <HR>
  47. <P>
  48. <H3><A NAME="SEC4" HREF="bull3_toc.html#SEC4">GNU'S BULLETIN</A></H3>
  49. <P>
  50. Copyright (C) June 1987 by the Free Software Foundation.
  51. <P>
  52. Editor: Paul Rubin<BR>
  53. Writers: Richard M. Stallman, Paul Rubin
  54. Illustrations: Etienne Suvasa, Jean-Marie Diaz.<BR>
  55. Reproduction: Mark D'Agostino.
  56. <P>
  57. <BLOCKQUOTE>
  58. Permission is granted to anyone to make or distribute verbatim
  59. copies of this document as received, in any medium, provided that
  60. the copyright notice and permission notice are preserved, and
  61. that the distributor grants the recipient permission for further
  62. redistribution as permitted by this notice.
  63. </BLOCKQUOTE>
  64. <P>
  65. <H1><A NAME="SEC5" HREF="bull3_toc.html#SEC5">What is the Free Software Foundation?</A></H1>
  66. <h2>By Richard M. Stallman</H2>
  67. <P>
  68. The Free Software Foundation is dedicated to eliminating restrictions
  69. on copying, redistribution, understanding and modification of software.
  70. <P>
  71. The word "free" in our name does not refer to price; it refers to
  72. freedom. First, the freedom to copy a program and redistribute it to
  73. your neighbors, so that they can use it as well as you. Second, the
  74. freedom to change a program, so that you can control it instead of it
  75. controlling you; for this, the source code must be made available to
  76. you.
  77. <P>
  78. The Foundation works to give you these freedoms by developing free
  79. compatible replacements for proprietary software. Specifically, we
  80. are putting together a complete, integrated software system "GNU" that
  81. is upward-compatible with Unix. When it is released, everyone will be
  82. permitted to copy it and distribute it to others; in addition, it will
  83. be distributed with source code, so you will be able to learn about
  84. operating systems by reading it, to port it to your own machine, to
  85. improve it, and to exchange the changes with others.
  86. <P>
  87. There are already organizations that distribute free CPM and MSDOS
  88. software. The Free Software Foundation is doing something different.
  89. <P>
  90. <OL>
  91. <LI>
  92. The other organizations exist primarily for distribution; they
  93. distribute whatever happens to be available. We hope to provide a
  94. complete integrated free system that will eliminate the need for any
  95. proprietary software.
  96. <P>
  97. <LI>
  98. One consequence is that we are now interested only in software
  99. that fits well into the context of the GNU system. Distributing
  100. free MSDOS or Macintosh software is a useful activity, but it is
  101. not part of our game plan.
  102. <P>
  103. <LI>
  104. Another consequence is that we will actively attempt to improve and
  105. extend the software we distribute, as fast as our manpower permits.
  106. For this reason, we will always be seeking donations of money,
  107. computer equipment or time, labor, and source code to improve the GNU
  108. system.
  109. <P>
  110. <LI>
  111. In fact, our primary purpose is this software development effort;
  112. distribution is just an adjunct which also brings in some money. We
  113. think that the users will do most of the distribution on their own,
  114. without needing or wanting our help.
  115. </OL>
  116. <P>
  117. <H3><A NAME="SEC6" HREF="bull3_toc.html#SEC6">Why a Unix-Like System?</A></H3>
  118. <P>
  119. It is necessary to be compatible with some widely used system to give
  120. our system an immediate base of trained users who could switch to it
  121. easily and an immediate base of application software that can run on
  122. it. (Eventually we will provide free replacements for proprietary
  123. application software as well, but that is some years in the future.)
  124. <P>
  125. We chose Unix because it is a fairly clean design which is already
  126. known to be portable, yet whose popularity is still rising. The
  127. disadvantages of Unix seem to be things we can fix without removing
  128. what is good in Unix.
  129. <P>
  130. Why not imitate MSDOS or CP/M? They are more widely used, true, but
  131. they are also very weak systems, designed for tiny machines. Unix is
  132. much more powerful and interesting. When a system takes years to
  133. implement, it is important to write it for the machines that will
  134. become available in the future; not to let it be limited by the
  135. capabilities of the machines that are in widest use at the moment but
  136. will be obsolete when the new system is finished.
  137. <P>
  138. Why not aim for a new, more advanced system, such as a Lisp Machine?
  139. Mainly because that is still more of a research effort; there is a
  140. sizeable chance that the wrong choices will be made and the system
  141. will turn out not very good. In addition, such systems are often tied
  142. to special hardware. Being tied to one manufacturer's machine would
  143. make it hard to remain independent of that manufacturer and get broad
  144. community support.
  145. <P>
  146. <H1><A NAME="SEC7" HREF="bull3_toc.html#SEC7">Editorial: Oppose Audio Copy Protection</A></H1>
  147. <P>
  148. Just when science is making it possible to copy music perfectly,
  149. record companies are trying to make it impossible again, with
  150. government-enforced copy protection.
  151. <P>
  152. The invention of the phonograph created a situation where the best way
  153. to copy audio signals was by mass production. This temporary
  154. situation made record companies necessary and useful. It also made
  155. copyright a fairly harmless way of encouraging activities that benefit
  156. the public. (That was the original purpose of copyright.)
  157. <P>
  158. Digital audio tape machines will change all this. Mass produced
  159. copies will no longer be better than you can make. Record companies
  160. may still have customers, but they will be partly obsolete.
  161. <P>
  162. But obsolete institutions don't peacefully accept being ignored. So
  163. there is a bill before Congress to require specific copy-protection
  164. equipment in every digital audio tape machine.
  165. <P>
  166. The proposed technical method involves degrading the quality of
  167. prerecorded music by eliminating a narrow frequency band. When the
  168. recorder notices that band is empty, it will shut off. Even if the
  169. signal comes over the radio, copying it will be impossible.
  170. <P>
  171. If this law passes, we can expect more of the same. In the past,
  172. there were many natural obstacles to copying information, and
  173. surmounting the obstacles was a business. The overall thrust of the
  174. information revolution is to remove these obstacles; to make
  175. information easy to copy and transform. Each time technology makes
  176. things easier, businesses that depend on obstacles demand a man-made
  177. obstacle--required by law--to replace the natural one.
  178. <P>
  179. A few general-purpose I/O devices can turn your computer into a
  180. digital audio tape recorder. Will there be a law to make this
  181. impossible? Perhaps a law that you can't have source to your kernel,
  182. lest you patch around the government-imposed access control?
  183. <P>
  184. To fight this bill, call your Congressman and Senators and urge them
  185. to vote against it. It is called the Digital Audio Tape Recording
  186. Act of 1987: S. 506, H.R. 1384.
  187. <P>
  188. You can get the phone numbers by calling information; the Senators
  189. usually have offices in the state capitol. For more information,
  190. contact this organization:
  191. <P>
  192. <PRE>
  193. Audio Recording Rights Coalition
  194. PO Box 33705
  195. 1145 19th Street NW
  196. Washington, DC 20033
  197. 1-800-282-TAPE
  198. </PRE>
  199. <P>
  200. <H1><A NAME="SEC8" HREF="bull3_toc.html#SEC8">Gnus Flashes</A></H1>
  201. <P>
  202. This is a collection of news items pertaining to the GNU project, the
  203. Free Software Foundation, and free software in general.
  204. <P>
  205. <UL>
  206. <LI>
  207. <B>Termcap Manual Being Published</B>
  208. <P>
  209. Jim Joyce's Unix bookstore in San Francisco is probably going to publish
  210. the Termcap programming manual written by Richard Stallman. This manual
  211. was written as a spinoff of the Emacs project, since the Unix documentation
  212. for Termcap does not provide enough information. The Foundation will
  213. probably offer printed copies of this manual for sale after Jim Joyce has
  214. gotten them printed. Like everything else written at GNU, the manual will
  215. be free for everyone to copy; however, Jim plans to donate some money to
  216. RMS for every copy he sells.
  217. <P>
  218. <LI><B>GNU Chess Improved</B>
  219. <P>
  220. Stuart Cracraft reports that as a result of his installing new searching
  221. and evaluation routines in GNU Chess, the latest version recently beat an 1800
  222. rated player. He is collecting contributions of book openings, endgame
  223. databases, and master games, to further improve the program. Contact him if
  224. you think you can help. His address is cracraft@venera.isi.edu.
  225. <P>
  226. <LI><B>If You Can't Beat 'em...</B>
  227. <P>
  228. RMS was recently invited to give a talk about GNU at AT&#38;T Bell Laboratories
  229. in Murray Hill, New Jersey (the birthplace of Un*x). He reports that the
  230. talk was generally well received.
  231. <P>
  232. <LI>
  233. <B>X Becoming Accepted</B>
  234. <P>
  235. The trade press has been reporting that the free X window system written at
  236. MIT and DEC is becoming a multi-vendor industry standard for portable
  237. window systems. The Foundation distributes X on its standard software
  238. tape, and GNU Emacs and GNU Chess come with special interfaces to X.
  239. <P>
  240. <LI>
  241. <B>TeX in C available from Pat Monardo</B>
  242. <P>
  243. At long last, there is a free implementation of TeX in C. It is a
  244. hand translation by Pat Monardo of UC Berkeley of the WEB version, and
  245. it tries to retain the module and variable names of the WEB version
  246. while remaining a readable C program. Both the Foundation and the
  247. maintainers of the Unix TeX distribution at the University of
  248. Washington will offer this version eventually. You can also contact
  249. Pat Monardo directly for more information. His address is
  250. ucbvax!monardo (uucp), or monardo@ucbvax.berkeley.edu (Internet).
  251. <P>
  252. Consider sending a donation to Pat if you find this program useful.
  253. <P>
  254. <LI>
  255. <B>Victory in SoftKlone trial</B>
  256. <P>
  257. A Federal Judge has found the SoftKlone company not guilty of nearly all
  258. counts of copyright infringement brought in a look-and-feel suit filed
  259. by the marketers of Crosstalk (a PC communications program). Even
  260. though the SoftKlone program is proprietary, the outcome of this trial
  261. is an important affirmation of everyone's freedom to write and
  262. distribute whatever programs they want to.
  263. <P>
  264. <LI>
  265. <B>Send In The Clones</B>
  266. <P>
  267. Meanwhile, the Lotus look-and-feel copywrong suit has still not been
  268. resolved. In order to help the defendants of this suit, Dan Bricklin
  269. is compiling a list of software and hardware "clones". These are
  270. programs and machines that duplicate the functionality, features, or
  271. "look and feel" of previously-released programs. (Dan is the author of
  272. VisiCalc, of which Lotus 1-2-3 is itself a partial clone). The
  273. Foundation is asking readers to please think of as many <EM>detailed</EM>
  274. examples as they can and mail them electronically to:
  275. <PRE>
  276. send-in-the-clones@prep.ai.mit.edu (Internet),
  277. </PRE>
  278. or
  279. <PRE>
  280. mit-eddie!mit-prep!send-in-the-clones (uucp).
  281. </PRE>
  282. or by snail mail to
  283. <PRE>
  284. Send In The Clones
  285. c/o Free Software Foundation
  286. 1000 Mass Ave.
  287. Cambridge, MA 02138
  288. </PRE>
  289. We will forward all the messages we receive to Dan Bricklin.
  290. <P>
  291. Here are some of the examples we already have, to give people an idea of
  292. what we're looking for:
  293. <P>
  294. <UL>
  295. <LI>
  296. CPU's made by Amdahl and others that emulate IBM mainframes.
  297. <LI>
  298. Ashton-Tate "Multiplan", which includes some features of the Wang
  299. dedicated word processor
  300. <LI>
  301. Richard Stallman's EMACS editor has been imitated any number of times.
  302. <LI>
  303. Imitations of the IBM PC BIOS run in nearly all PC clones.
  304. The PC clones would be useless without doing this.
  305. <LI>
  306. The Unix user interface has been imitated many times, both in complete
  307. systems (Idris, Coherent, Minix, MARC, GNU, etc.) and in program suites
  308. that just clone the utilities (e.g. Software Tools; nearly every
  309. microcomputer C compiler I've seen comes with a few of these).
  310. <LI>
  311. All C compilers implement a special language (C) that used to be
  312. available only as part of Unix.
  313. </UL>
  314. <P>
  315. Non-computer examples (such as the many imitations of the
  316. Sony Walkman) are ok too.
  317. <P>
  318. </UL>
  319. <P>
  320. <H1><A NAME="SEC9" HREF="bull3_toc.html#SEC9">GNU Software Available Now</A></H1>
  321. <P>
  322. <UL>
  323. <LI>
  324. <B>GNU Emacs</B>
  325. <P>
  326. In 1975, Richard Stallman developed the first Emacs: the extensible,
  327. customizable real-time display editor. GNU Emacs is his second
  328. implementation of Emacs. It's the first Emacs available on Unix
  329. systems which offers true Lisp, smoothly integrated into the editor,
  330. for writing extensions. It also provides a special interface to
  331. MIT's free X window system, which makes redisplay very fast.
  332. <P>
  333. GNU Emacs has been in widespread use since 1985 and often, as at
  334. MIT's Project Athena, displaces proprietary implementations of Emacs
  335. because of its greater reliability as well as its good features
  336. and easier extensibility.
  337. <P>
  338. GNU Emacs has run on many kinds of Unix systems: those made by Alliant
  339. (system release 1 or 2), Amdahl (UTS), AT&#38;T (3b machines and 7300 pc),
  340. Celerity, Digital (Vax, not PDP-11), Dual, Encore, Gould, HP (9000 series
  341. 200 or 300 but not series 500), IBM (RT/PC running 4.2), Integrated
  342. Solutions (Optimum V with 68020 and VMEbus), Masscomp, Megatest, NCR (Tower
  343. 32), Plexus, Pyramid, Sequent, Silicon Graphics (Iris release 3.5), Stride
  344. (system release 2), Sun (any kind), Tahoe, Tektronix (NS16000 system),
  345. Texas Instruments (Nu), Whitechapel (MG1), and Wicat. These include both
  346. Berkeley Unix and System V (release 0, 2 or 2.2). It also runs on Apollo
  347. machines and on VAX/VMS.
  348. <P>
  349. GNU Emacs use is described by the GNU Emacs Manual, available from
  350. the Free Software Foundation.
  351. <P>
  352. <LI>
  353. <B>GDB</B>
  354. <P>
  355. GDB is the source-level C debugger written for the GNU project in 1986. It
  356. offers many features not usually found in debuggers on Unix, such as a
  357. history that records all values examined within the debugger for concise
  358. later reference, multi-line user-defined commands, and a strong
  359. self-documentation capability. It currently runs on Vaxes under 4.2 and
  360. 4.3bsd, and on Suns (systems version 2 and 3). A version for the IBM RT-PC
  361. running 4.2bsd may be released soon.
  362. <P>
  363. A users' manual for GDB is available from the Foundation.
  364. <P>
  365. <LI>
  366. <B>GNU CC</B>
  367. <P>
  368. The GNU C compiler is a fairly portable optimizing compiler. It generates
  369. good code for the 68000, 68020 and Vax. It features automatic register
  370. packing that makes register declarations unnecessary. It supports full
  371. ANSI C as of the latest draft standard. We are offering a beta test
  372. release to people wishing to help us find compiler bugs or begin work on
  373. ports. This testing version is distributed on a separate tape from the
  374. regular GNU distribution. When the compiler is more solid, it will become
  375. part of the regular tape.
  376. <P>
  377. <LI>
  378. <B>Bison</B>
  379. <P>
  380. Bison is an upward-compatible replacement for YACC, with some
  381. additional as-yet-undocumented features. It has been in use for a
  382. couple of years.
  383. <P>
  384. <LI>
  385. <B>X Window System</B>
  386. <P>
  387. X is a portable, network transparent window system for bitmap displays
  388. written at MIT and DEC. It currently runs on DEC VAXstation, Lexidata
  389. 90, and most Sun Microsystems displays, with others in the works. X
  390. supports overlapping windows, fully recursive subwindows, and provides
  391. hooks for several different styles of user interface. Applications
  392. provided include a terminal emulator, bitmap editor, several window
  393. managers, clock, window dump and undump programs, hardcopy printing
  394. program for the LN03 printer, several typesetting previewers, etc.
  395. <P>
  396. <LI>
  397. <B>MIT Scheme</B>
  398. <P>
  399. Scheme is a simplified, lexically scoped dialect of Lisp, designed at
  400. MIT and other universities for two purposes: teaching students of
  401. programming, and researching new parallel programming constructs
  402. and compilation techniques. MIT Scheme is written in C and runs on
  403. many kinds of Unix systems.
  404. <P>
  405. Sorry, there is no documentation for the current distribution version
  406. of MIT Scheme. A new standard for Scheme has been designed by the
  407. various labs that work on Scheme, and work is going on at MIT to
  408. change MIT Scheme to fit. Once that is done, the standard will serve
  409. as a manual for MIT Scheme. At that time, we will distribute both the
  410. new release of Scheme and the standard.
  411. <P>
  412. <LI>
  413. <B>GNU Chess</B>
  414. <P>
  415. GNU Chess was written in 1986 by Stuart Cracraft of UCLA. It can use
  416. several machines in parallel for increased searching speed, and it
  417. comes with an interface to the X window system to display a pretty
  418. chessboard. It also has a human readable opening book of thousands of
  419. moves including several hundred games of Grandmaster Mikhail Tal. On
  420. a single Sun-3 CPU, the current version probably plays around Class C
  421. chess. Stuart continues to strengthen the program in various ways.
  422. <P>
  423. <LI>
  424. <B>Hack</B>
  425. <P>
  426. Hack is a display oriented adventure game similar to Rogue.
  427. </UL>
  428. <P>
  429. <H2><A NAME="SEC10" HREF="bull3_toc.html#SEC10">How To Get Gnu Software</A></H2>
  430. <P>
  431. All software and publications are distributed with permission to
  432. copy and redistribute. The easiest way to get a copy of GNU Software
  433. is from someone else who has it. You need not ask for permission;
  434. just copy it.
  435. <P>
  436. If you have access to the Internet, you can get the latest
  437. distribution version of GNU Software from host prep.ai.mit.edu. For
  438. more information, read the file <TT>`/u2/emacs/GETTING.GNU.SOFTWARE'</TT>
  439. on said host.
  440. <P>
  441. If you cannot get a copy in any of these ways, you can order one from the
  442. Free Software Foundation. Please consult the order form at the end of this
  443. bulletin for prices and details.
  444. <P>
  445. <H1><A NAME="SEC11" HREF="bull3_toc.html#SEC11">Status of the GNU Project, June 1987</A></H1>
  446. <P>
  447. (See also the article "GNU Software Available Now", elsewhere in this issue).
  448. <P>
  449. <UL>
  450. <P>
  451. <LI>
  452. <B>GNU Emacs and GDB</B>
  453. <P>
  454. GNU Emacs and GDB are already released. Berkeley is distributing GNU
  455. Emacs with the 4.3 distribution, and DEC is going to distribute it with
  456. Unix systems on Vaxes.
  457. <P>
  458. <LI>
  459. <B>Gsh, the GNU imitation C shell</B>
  460. <P>
  461. Beta-test release of a C shell with input editing and compilation of
  462. shell scripts is expected soon. It was delayed due to illness.
  463. <P>
  464. The same program is supposed to imitate sh, but that doesn't work yet.
  465. <P>
  466. <LI>
  467. <B>Kernel</B>
  468. <P>
  469. We are negotiating with Prof. Rashid of Carnegie-Mellon University
  470. about working with them on the development of the MACH kernel. MACH
  471. is a message passing kernel that will probably succeed 4.3bsd as the
  472. standard kernel used for ARPA-sponsored operating system research.
  473. If an agreement is reached, we will use MACH as the kernel of GNU;
  474. otherwise, we will probably use a free remote procedure call kernel
  475. called TRIX, which was written at MIT. TRIX runs, and supports basic
  476. Unix compatibility, but needs a lot of new features.
  477. <P>
  478. <LI>
  479. <B>C compiler</B>
  480. <P>
  481. RMS is now working on finishing a new portable optimizing C compiler. It
  482. supports the Oct 1986 draft of ANSI C and has compiled both itself and GNU
  483. Emacs. A second beta test version of the compiler has just been released.
  484. It fixes the bugs found in the March 1987 preliminary test release, but is
  485. still not considered ready for everyday use.
  486. <P>
  487. The compiler performs automatic register allocation, common
  488. subexpression elimination, invariant code motion from loops, constant
  489. propagation and copy propagation, delaying popping of function call
  490. arguments, tail recursion elimination, plus many local optimizations
  491. that are automatically deduced from the machine description. By the
  492. time it is finished it will probably also know when to keep constant
  493. addresses in registers. We may also make some rearrangements in order
  494. to enable compilation of arbitrarily large functions in bounded
  495. amounts of memory, though with some decrease in optimization compared
  496. to what can be done with lots of memory.
  497. <P>
  498. GCC makes shorter and faster 68020 code than the Sun compiler with -O.
  499. It makes shorter Vax code than the Tartan C compiler with -O4, but we
  500. haven't been able to compare the running speed of that code. Enough
  501. internal documentation is included for people interested in
  502. retargeting the compiler to other CPUs to get started.
  503. <P>
  504. Our cpp now supports the Oct 1986 draft standard.
  505. <P>
  506. <LI>
  507. <B>Assembler</B>
  508. <P>
  509. We have a partially-portable one-pass assembler that is almost
  510. twice as fast as the Unix assembler. It now works for Vaxes and
  511. the 68020.
  512. <P>
  513. <LI>
  514. <B>Window system</B>
  515. <P>
  516. We plan to use the X window system written at MIT. This system
  517. is already available free.
  518. <P>
  519. <LI>
  520. <B>Documentation system</B>
  521. <P>
  522. We now have a truly compatible pair of programs which can convert a
  523. file of texinfo format documentation into either a printed manual or
  524. an Info file. A Texinfo manual which describes how to write documents
  525. in Texinfo is available from the Foundation.
  526. <P>
  527. Documentation files are needed for many utilities.
  528. <P>
  529. <LI>
  530. <B>Other Utilities</B>
  531. <P>
  532. The GNU `ls', `grep', `awk', `make' and `ld' are in regular use.
  533. The other object-file management utilities are written too. Our
  534. free replacement for `yacc' is called `bison'. `cron' and `at' were
  535. recently submitted, and so was `m4'. `lex' is expected in June.
  536. <P>
  537. A free stdio system has just been received.
  538. <P>
  539. <LI>
  540. <B>Free Software Foundation</B>
  541. <P>
  542. The foundation exists for two purposes: to accept gifts to support GNU
  543. development, and to carry out distribution. We are now tax exempt;
  544. you can deduct donations to us on your tax returns.
  545. <P>
  546. Our address is
  547. <PRE>
  548. Free Software Foundation
  549. 1000 Mass Ave
  550. Cambridge, MA 02138
  551. </PRE>
  552. and our phone number is (617) 876-3296.
  553. <P>
  554. Because of the confusion surrounding LMI's change of ownership, our phone
  555. service was temporarily interrupted in May. We are still trying to
  556. straighten everything out with the phone company. If you called us and got
  557. a recording saying our number was disconnected, please keep trying. We
  558. haven't gone out of business!
  559. <P>
  560. <LI>
  561. <B>Service directory</B>
  562. <P>
  563. The foundation now maintains a Service Directory; a list of people
  564. who offer service to individual users of GNU Emacs and, eventually,
  565. all parts of the GNU system. Service can be answering questions
  566. for new users, customizing programs, porting to new systems, or
  567. anything else.
  568. <P>
  569. <LI>
  570. <B>Possible target machines</B>
  571. <P>
  572. GNU will require a cpu that uses 32-bit addresses and integers and
  573. addresses to the 8-bit byte. 1 meg of core should be enough, though
  574. currently the GNU C compiler can require several meg for a large
  575. function. Unless we do a lot of work to fix this you probably need
  576. to have virtual memory. MACH also requires virtual memory.
  577. <P>
  578. GNU Emacs requires more than a meg of addressable memory in the system,
  579. although a meg of physical memory is probably enough if there is virtual
  580. memory.
  581. <P>
  582. A hard disk will be essential; at least 40 meg will be needed to hold the
  583. system plus the source code plus the manual plus swapping space. Plus more
  584. space for the user's files, of course. The system binaries will probably
  585. fit in around 10 meg. We recommend 80 meg or more for a personal GNU system.
  586. <P>
  587. This is not to say that it will be impossible to adapt some or all of GNU
  588. for other kinds of machines; but it may be difficult, and we don't consider
  589. it part of our job to try to reduce that difficulty.
  590. <P>
  591. We have nothing to say about any specific models of microcomputer,
  592. as we do not follow hardware products.
  593. <P>
  594. <LI>
  595. <B>Porting</B>
  596. <P>
  597. It is too early to inquire about porting GNU (except GNU Emacs
  598. and GNU CC). First, we have to finish it.
  599. </UL>
  600. <P>
  601. <H2><A NAME="SEC12" HREF="bull3_toc.html#SEC12">Why Was Copyright Invented?</A></H2>
  602. <P>
  603. Now that copyright is becoming a public nuisance that the public tries
  604. to ignore, copyright owners try to justify this imposition by calling
  605. it an intrinsic right. As they tell it, their intrinsic right is a
  606. tradition that makes the public good irrelevant.
  607. <P>
  608. This is contrary to the facts of the history of copyright.
  609. <P>
  610. The Supreme Court has stated explicitly what copyright was for.
  611. Writing for the Court, Justice Stewart explained:
  612. <P>
  613. <BLOCKQUOTE>
  614. The immediate effect of our copyright law is to secure a fair return
  615. for an "author's" creative labor. But the ultimate aim is, by this
  616. incentive, to stimulate artistic creativity for the general public good.
  617. `The sole interest of the United States and the primary object in
  618. conferring the [copyright] monopoly,' this Court has said, `lie in the
  619. general benefits derived by the public from the labors of authors.'
  620. </BLOCKQUOTE>
  621. <PRE>
  622. <TT> </TT>---Fox Film Corp. v. Doyal (286 US 123, 127)
  623. </PRE>
  624. <P>
  625. So when copyright interferes with the public use of a program, that
  626. directly attacks the reason for having copyright.
  627. <P>
  628. <H1><A NAME="SEC13" HREF="bull3_toc.html#SEC13">What is GNU Emacs and do you want a copy?</A></H1>
  629. <P>
  630. GNU Emacs is a new implementation of the Emacs text editor.
  631. (Recently text editors have been called "word processors" among
  632. microcomputer users.)
  633. <P>
  634. Emacs is a kind of architecture for text editors, in which most
  635. editing commands are written in an interpreted language (usually
  636. Lisp) so that the user can write new editing commands as he goes.
  637. This allows Emacs to have editing commands that are more powerful
  638. or more adapted to individual uses than other kinds of editors.
  639. <P>
  640. Any particular editing command could be written in C, but with
  641. Lisp it is much easier for users to change the editing commands
  642. or to implement new editing commands. Users can also exchange
  643. their adaptations and extensions of Emacs. The result is a library
  644. of extensions that continues to grow.
  645. <P>
  646. GNU Emacs boasts an especially clean Lisp system for writing editing
  647. commands, and an already large library of extensions.
  648. <P>
  649. GNU Emacs is written in C, designed for a Unix or Unix-like
  650. kernel. It includes its own Lisp interpreter which is used to
  651. execute the portion of the editor that is written in Lisp.
  652. <P>
  653. It is a fairly large program, around 525k on vaxes or 68000s, to
  654. which must be added space for the files you are editing, undo
  655. buffers, Lisp libraries loaded, and Lisp data such as recently
  656. killed text, etc. This is not really a problem on a timeshared
  657. machine because most of that 525k is shared, but on a personal
  658. computer there may be nobody to share with. Thus, GNU Emacs
  659. probably could not be used on an IBM PC clone for lack of memory,
  660. unless you want to implement virtual memory in software within
  661. Emacs itself. Perhaps on an 80286 with 1 meg of memory you can
  662. win using their memory management.
  663. <P>
  664. In general, a 32-bit machine with either a meg of real memory
  665. or virtual memory can probably run GNU Emacs, as long as a suitable
  666. Unix system call environment is provided, simulated or imitated.
  667. <P>
  668. <H1><A NAME="SEC14" HREF="bull3_toc.html#SEC14">GNU Wish List</A></H1>
  669. <P>
  670. Wishes for this issue:
  671. <P>
  672. <UL>
  673. <LI>
  674. Money and equipment, as usual.
  675. <P>
  676. <LI>
  677. Some free office space in the Cambridge area.
  678. <P>
  679. <LI>
  680. Volunteer programming, especially from people around Cambridge and people
  681. with experience writing operating system kernels. Help writing
  682. documentation is also needed.
  683. <P>
  684. <LI>
  685. Artwork and other graphics, for use as illustrations in future FSF
  686. manuals and GNU's bulletins.
  687. <P>
  688. <LI>
  689. Would anyone like to edit GNU's Bulletin #4?
  690. </UL>
  691. <P>
  692. <H2><A NAME="SEC15" HREF="bull3_toc.html#SEC15">Thank Gnus</A></H2>
  693. <P>
  694. The Free Software Foundation would like to send special thank gnus to
  695. the following:
  696. <P>
  697. Thanks to the MIT Laboratory for Computer Science. The LCS has provided
  698. FSF with the loan of a Microvax for program development.
  699. <P>
  700. Thanks to Professor Dertouzos, head of LCS. His specific decision to
  701. support us is greatly appreciated.
  702. <P>
  703. Thanks to the MIT Artificial Intelligence Laboratory for invaluable
  704. assistance of many kinds.
  705. <P>
  706. Thanks to Lisp Machine, Inc. LMI has generously provided office space,
  707. computer resources and a mailing address for FSF. Bruce Deffenbaugh
  708. in particular helped us keep our operation in relative calm during
  709. LMI's recent turmoil.
  710. <P>
  711. Thanks to Inference Corp. Inference has been shipping copies of GNU
  712. Emacs to its customers in conjunction with some other products that
  713. they offer, and they have decided to donate $200 to Richard Stallman
  714. for each copy of Emacs they deliver in this way. This proves it is
  715. possible to make a living from writing free software.
  716. <P>
  717. Thanks to Martin Minow of DEC for giving us an answering machine, so
  718. people can now phone us at (617) 876-3296. We check messages about
  719. once a week.
  720. <P>
  721. Thanks to those who sent money and offered help. James R. Payne of
  722. Advanced Decision Systems gave especially freely. Thanks also to those
  723. who support us by ordering Emacs manuals and distribution tapes.
  724. <P>
  725. The creation of this bulletin is our way of thanking all who have
  726. expressed interest in what we are doing.
  727. <P>
  728. <HR>