DOCSLIB.ORG

Allegro-Manual-4.2.1.En.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Allegro-Manual-4.2.1.En.Pdf ______ ___ ___ /\ _ \ /\_ \ /\_ \ \ \ \L\ \\//\ \ \//\ \ __ __ _ __ ___ \ \ __ \ \ \ \ \ \ \ /’__‘\ /’_ ‘\/\‘’__\/ __‘\ \ \ \/\ \ \_\ \_ \_\ \_/\ __//\ \L\ \ \ \//\ \L\ \ \ \_\ \_\/\____\/\____\ \____\ \____ \ \_\\ \____/ \/_/\/_/\/____/\/____/\/____/\/___L\ \/_/ \/___/ /\____/ \_/__/ Version 4.2.1 A game programming library. By Shawn Hargreaves, Nov 26, 2006. See the AUTHORS file for a complete list of contributors. #include <std disclaimer.h> "I do not accept responsibility for any effects, adverse or otherwise, that this code may have on you, your computer, your sanity, your dog, and anything else that you can think of. Use it at your own risk." Chapter 1: API 1 1 API 1.1 Using Allegro See readme.txt for a general introduction, copyright details, and information about how to install Allegro and link your program with it. 1.1.1 install allegro int install_allegro(int system_id, int *errno_ptr, int (*atexit_ptr)()); Initialises the Allegro library. You must call either this or allegro init() before doing anything other than using the Unicode routines. If you want to use a text mode other than UTF-8, you can set it with set uformat() before you call this. The other functions that can be called before this one will be marked explicitly in the documentation, like set config file(). The available system ID codes will vary from one platform to another, but you will almost always want to pass SYSTEM AUTODETECT. Alternatively, SYSTEM NONE installs a stripped down version of Allegro that won’t even try to touch your hardware or do anything platform specific: this can be useful for situations where you only want to manipulate memory bitmaps, such as the text mode datafile tools or the Windows GDI interfacing functions. The ‘errno ptr’ and ‘atexit ptr’ parameters should point to the errno variable and atexit function from your libc: these are required because when Allegro is linked as a DLL, it doesn’t have direct access to your local libc data. ‘atexit ptr’ may be NULL, in which case it is your responsibility to call allegro exit() man- ually. Example: install_allegro(SYSTEM_AUTODETECT, &errno, atexit); This function returns zero on success and non-zero on failure (e.g. no system driver could be used). Note: in previous versions of Allegro this function would abort on error. See also: See Section 1.1.2 [allegro init], page 1. See Section 1.1.3 [allegro exit], page 2. See Section 1.3.1 [set uformat], page 26. See Section 1.4.1 [set config file], page 51. 1.1.2 allegro init int allegro_init(); Macro which initialises the Allegro library. This is the same thing as calling install allegro(SYSTEM AUTODETECT, &errno, atexit). See also: See Section 1.1.1 [install allegro], page 1. 2 Allegro Manual See Section 1.1.3 [allegro exit], page 2. See Section 3.4 [Available], page 397. 1.1.3 allegro exit void allegro_exit(); Closes down the Allegro system. This includes returning the system to text mode and removing whatever mouse, keyboard, and timer routines have been installed. You don’t normally need to bother making an explicit call to this function, because allegro init() installs it as an atexit() routine so it will be called automatically when your program exits. Note that after you call this function, other functions like destroy bitmap() will most likely crash. This is a problem for C++ global destructors, which usually get called after atexit(), so don’t put Allegro calls in them. You can write the destructor code in another method which you can manually call before your program exits, avoiding this problem. See also: See Section 1.1.1 [install allegro], page 1. See Section 1.1.2 [allegro init], page 1. See Section 1.10.9 [destroy bitmap], page 127. See Section 3.4.34 [ex3d], page 430. See Section 3.4.38 [exscn3d], page 435. See Section 3.4.47 [exswitch], page 447. See Section 3.4.31 [exxfade], page 426. See Section 3.4.39 [exzbuf], page 437. 1.1.4 END OF MAIN Macro END_OF_MAIN() In order to maintain cross-platform compatibility, you have to put this macro at the very end of your main function. This macro uses some ‘magic’ to mangle your main procedure on platforms that need it like Windows, some flavours of UNIX or MacOS X. On the other platforms this macro compiles to nothing, so you don’t have to #ifdef around it. Example: int main(void) { allegro_init(); /* more stuff goes here */ ... return 0; } END_OF_MAIN() Chapter 1: API 3 See also: See Section 2.2 [Windows], page 365. See Section 2.3 [Unix], page 374. See Section 2.6 [MacOS], page 382. See Section 2.7 [Differences], page 384. See Section 3.4 [Available], page 397. 1.1.5 allegro id extern char allegro_id[]; Text string containing a date and version number for the library, in case you want to display these somewhere. 1.1.6 allegro error extern char allegro_error[ALLEGRO_ERROR_SIZE]; Text string used by set gfx mode(), install sound() and other functions to re- port error messages. If they fail and you want to tell the user why, this is the place to look for a description of the problem. Example: void abort_on_error(const char *message) { if (screen != NULL) set_gfx_mode(GFX_TEXT, 0, 0, 0, 0); allegro_message("%s.\nLast Allegro error ‘%s’\n", message, allegro_error); exit(-1); } ... if (some_allegro_function() == ERROR_CODE) abort_on_error("Error calling some function!"); See also: See Section 1.9.7 [set gfx mode], page 110. See Section 1.25.5 [install sound], page 245. See Section 3.4 [Available], page 397. 1.1.7 ALLEGRO VERSION #define ALLEGRO_VERSION Defined to the major version of Allegro. From a version number like 4.1.16, this would be defined to the integer 4. 4 Allegro Manual 1.1.8 ALLEGRO SUB VERSION #define ALLEGRO_SUB_VERSION Defined to the middle version of Allegro. From a version number like 4.1.16, this would be defined to the integer 1. 1.1.9 ALLEGRO WIP VERSION #define ALLEGRO_WIP_VERSION Defined to the minor version of Allegro. From a version number like 4.1.16, this would be defined to the integer 16. 1.1.10 ALLEGRO VERSION STR #define ALLEGRO_VERSION_STR Defined to a text string containing all version numbers and maybe some ad- ditional text. This could be ‘4.1.16 (CVS)’ for an Allegro version obtained straight from the CVS repository. 1.1.11 ALLEGRO DATE STR #define ALLEGRO_DATE_STR Defined to a text string containing the year this version of Allegro was released, like ‘2004’. 1.1.12 ALLEGRO DATE #define ALLEGRO_DATE Defined to an integer containing the release date of Allegro in the packed format ‘yyyymmdd’. Example: const int year = ALLEGRO_DATE / 10000; const int month = (ALLEGRO_DATE / 100) % 100; const int day = ALLEGRO_DATE % 100; allegro_message("Year %d, month %d, day %d\n", year, month, day); 1.1.13 AL ID Macro AL_ID(a,b,c,d) This macro can be used to create a packed 32 bit integer from 8 bit characters, on both 32 and 64 bit machines. These can be used for various things, like custom datafile objects or system IDs. Example: #define OSTYPE_LINUX AL_ID(’T’,’U’,’X’,’ ’) See also: See Section 1.32.13 [DAT ID], page 304. Chapter 1: API 5 1.1.14 MAKE VERSION Macro MAKE_VERSION(a, b, c) This macro can be used to check if some Allegro version is (binary) compatible with the current version. It is safe to use > and < to check if one version is more recent than another. The third number is ignored if the second number is even, so MAKE VERSION(4, 2, 0) is equivalent to MAKE VERSION(4, 2, 1). This is because of our version numbering policy since 4.0.0: the second number is even for stable releases, which must be ABI-compatible with earlier versions of the same series. This macro is mainly useful for addon packages and libraries. See the ‘ABI compatibility information’ section of the manual for more detailed information. Example: /* Check if the current version is compatible with Allegro 4.2.0 */ #if (MAKE_VERSION(4, 2, 0) <= MAKE_VERSION(ALLEGRO_VERSION, \ ALLEGRO_SUB_VERSION, ALLEGRO_WIP_VERSION)) /* Allegro 4.2.0 compatibility */ #else /* Work-around */ #endif See also: See Section 1.1.7 [ALLEGRO VERSION], page 3. See Section 1.1.8 [ALLEGRO SUB VERSION], page 4. See Section 1.1.9 [ALLEGRO WIP VERSION], page 4. 1.1.15 os type extern int os_type; Set by allegro init() to one of the values: OSTYPE_UNKNOWN - unknown, or regular MSDOS OSTYPE_WIN3 - Windows 3.1 or earlier OSTYPE_WIN95 - Windows 95 OSTYPE_WIN98 - Windows 98 OSTYPE_WINME - Windows ME OSTYPE_WINNT - Windows NT OSTYPE_WIN2000 - Windows 2000 OSTYPE_WINXP - Windows XP OSTYPE_WIN2003 - Windows 2003 OSTYPE_WINVISTA - Windows Vista OSTYPE_OS2 - OS/2 OSTYPE_WARP - OS/2 Warp 3 OSTYPE_DOSEMU - Linux DOSEMU OSTYPE_OPENDOS - Caldera OpenDOS OSTYPE_LINUX - Linux 6 Allegro Manual OSTYPE_SUNOS - SunOS/Solaris OSTYPE_FREEBSD - FreeBSD OSTYPE_NETBSD - NetBSD OSTYPE_IRIX - IRIX OSTYPE_DARWIN - Darwin OSTYPE_QNX - QNX OSTYPE_UNIX - Unknown Unix variant OSTYPE_BEOS - BeOS OSTYPE_MACOS - MacOS OSTYPE_MACOSX - MacOS X See also: See Section 1.1.2 [allegro init], page 1. See Section 1.1.16 [os version], page 6. See Section 1.1.17 [os multitasking], page 6. 1.1.16 os version extern int os_version; extern int os_revision; The major and minor version of the Operating System currently running. Set by allegro init(). If Allegro for some reason was not able to retrieve the version of the Operating System, os version and os revision will be set to -1. For example: Under Win98 SE (v4.10.2222) os version will be set to 4 and os revision to 10. See also: See Section 1.1.15 [os type], page 5.
Load more

Recommended publications
  • The Blit: a Multiplexed Graphics Terminal
    The Blit: A Multiplexed Graphics Terminal Rob Pike Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT The Blit is a programmable bitmap graphics terminal designed specifically to run with the Unix operating system. The software in the terminal provides an asynchronous multi-window environment, and thereby exploits the multiprogramming capabilities of the Unix system which have been largely under-utilized because of the restrictions of conventional terminals. This paper discusses the design motivation of the Blit, gives an overview of the user interface, mentions some of the novel uses of multiprogramming made possible by the Blit, and describes the implementation of the multiplexing facilities on the host and in the terminal. Because most of the functionality is provided by the ter- minal, the discussion focuses on the structure of the terminal’s software. Sometime in 1983 The Blit: A Multiplexed Graphics Terminal Rob Pike Bell Laboratories Murray Hill, New Jersey 07974 Introduction The Blit* is a graphics terminal characterized more by the software it runs than the hardware itself. The hardware is simple and inexpensive (Figure 1): 256K bytes of memory dual-ported between an 800×1024×1 bit display and a Motorola MC68000 microprocessor, with 24K of ROM, an RS-232 interface, a mouse and a keyboard. Unlike many graphics terminals, it has no special-purpose graphics hardware; instead, the microprocessor executes all graphical operations in software. The reasons for and conse- quences of this design are discussed elsewhere.5 The microprocessor may be loaded from the host with custom applications software, but the terminal is rarely used this way.
    [Show full text]
  • A Complete Bibliography of Publications in Software—Practice and Experience
    A Complete Bibliography of Publications in Software|Practice and Experience Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 23 July 2021 Version 3.26 Title word cross-reference [Bar82a, Bar82c, Bar84b]. < [SMGMOFM07a, SMGMOFM07b]. > [SMGMOFM07a, SMGMOFM07b]. 2 [MST13, MDB19]. 3 [DS09]. 4 [MSR+07]. \ 0 [GW96]. 1 [GW96]. $1.50 [Bar78d]. $11 [PK04]. TM [MZB00, Win02]. 8 [DB21b]. k [Bar84a]. $12.00 [Rob72]. $13 [Bar84a]. [AW93, Mer93]. κ [MG94]. µ $13.00 [Rob72]. $18.50 [Jon74]. $185 [BS90c, BDS+92, SMNB21]. N [Bar79b]. $19.30 [Lan74a]. $19.50 [Dav78]. [MS98, Coh98, KST94, YAVHC21]. P 3 $25.00 [Pet77, And78]. 3 [BE02, FMA02]. [DC03]. PM [CLD+17]. q [GSR17]. τ $31-25 [Pet77]. $31.35 [Bri82]. 32 [VED06]. 2:5 [TSZ14, UDS+07]. $35.00 [Inc86]. $39.50 [Sim83]. 5 [CPMAH+20]. $58.50 [Wal81a]. $6.95 -ary [MS98]. -bit [AM10, SF85, VED06]. [Tho74]. 64 [AM10, VED06]. 68 -gram [Coh98, KST94, YAVHC21]. -grams [Ear76, Hol77]. $68.25 [Pit82]. $7.00 [GSR17]. -level [FM77]. -queens [Plu74]. [Bar72a]. $7.50 [Bar78d]. $7.95 -R [Ear76, Hol77]. -shortest-paths [MG94]. [Bar76a, Lav77]. $78.50 [Sim83]. 8 -System [BS90c]. [Plu74, SF85]. $8.95 [Bar82a, Bar82c, Bar84b]. $9.75 . [Bis81b]. .NET [Coo04, Han04]. [Bar77e, Mul76]. $9.80 [Atk79a]. $9.95 1 2 0 [Bar81, Edw98a, Edw98b, Gru83, Llo82, 2 [Bar74a, Bar74b, Bar80b, Bud85, Cor88b, Val77a, Val78, Wal83b].
    [Show full text]
  • Acme: a User Interface for Programmers Rob Pike AT&T Bell Laboratories Murray Hill, New Jersey 07974
    Acme: A User Interface for Programmers Rob Pike AT&T Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT A hybrid of window system, shell, and editor, Acme gives text-oriented applications a clean, expressive, and consistent style of interaction. Traditional window systems support inter- active client programs and offer libraries of pre-defined operations such as pop-up menus and buttons to promote a consistent user interface among the clients. Acme instead provides its clients with a fixed user interface and simple conventions to encourage its uniform use. Clients access the facilities of Acme through a file system interface; Acme is in part a file server that exports device-like files that may be manipulated to access and control the contents of its win- dows. Written in a concurrent programming language, Acme is structured as a set of communi- cating processes that neatly subdivide the various aspects of its tasks: display management, input, file server, and so on. Acme attaches distinct functions to the three mouse buttons: the left selects text; the mid- dle executes textual commands; and the right combines context search and file opening functions to integrate the various applications and files in the system. Acme works well enough to have developed a community that uses it exclusively. Although Acme discourages the traditional style of interaction based on typescript windows— teletypes—its users find Acme’s other services render typescripts obsolete. History and motivation The usual typescript style of interaction with Unix and its relatives is an old one. The typescript—an inter- mingling of textual commands and their output—originates with the scrolls of paper on teletypes.
    [Show full text]
  • Micropython Documentation Release 1.10 Damien P. George, Paul
    MicroPython Documentation Release 1.10 Damien P. George, Paul Sokolovsky, and contributors Jan 25, 2019 CONTENTS 1 MicroPython libraries 1 1.1 Python standard libraries and micro-libraries..............................2 1.1.1 Builtin functions and exceptions................................2 1.1.2 array – arrays of numeric data................................5 1.1.3 cmath – mathematical functions for complex numbers....................5 1.1.4 gc – control the garbage collector...............................6 1.1.5 math – mathematical functions................................7 1.1.6 sys – system specific functions................................9 1.1.7 ubinascii – binary/ASCII conversions........................... 11 1.1.8 ucollections – collection and container types...................... 11 1.1.9 uerrno – system error codes................................. 12 1.1.10 uhashlib – hashing algorithms............................... 13 1.1.11 uheapq – heap queue algorithm................................ 14 1.1.12 uio – input/output streams................................... 14 1.1.13 ujson – JSON encoding and decoding............................ 16 1.1.14 uos – basic “operating system” services............................ 16 1.1.15 ure – simple regular expressions............................... 20 1.1.16 uselect – wait for events on a set of streams........................ 22 1.1.17 usocket – socket module................................... 23 1.1.18 ussl – SSL/TLS module................................... 28 1.1.19 ustruct – pack and unpack
    [Show full text]
  • Histoire D'unix
    Histoire d’Unix David du Colombier Jean-Baptiste Campesato 9 juillet 2008 Table des mati`eres 1 La gen`ese 2 1.1 Bell Labs . 2 1.2 Multics . 3 1.3 Ken’s New System . 3 1.4 Le langage B . 4 1.5 La naissance d’Unix Time-Sharing System . 4 1.6 Le langage C . 6 1.7 L’´evolution d’Unix Time-Sharing System . 6 2 L’expansion 8 2.1 Berkeley Software Distribution . 8 2.1.1 1BSD et 2BSD . 8 2.1.2 L’arriv´eede l’adressage sur 32 bits . 9 2.1.3 3BSD et 4BSD . 9 2.1.4 4BSD `a4.2BSD . 10 2.1.5 4.3BSD . 11 2.1.6 BSD Networking Release . 12 2.1.7 Le proc`es: USL vs. BSDI . 14 2.1.8 4.4BSD . 14 2.2 L’Unix de AT&T . 15 2.2.1 Les d´ebuts. 15 2.2.2 UNIX System V . 16 2.3 L’Unix de Sun Microsystems . 17 2.3.1 SunOS . 17 2.3.2 Solaris . 18 3 L’ouverture 19 3.1 Le tournant de Bell Labs . 19 3.1.1 La fin d’Unix Time-Sharing System . 19 3.1.2 Plan 9 from Bell Labs . 20 3.1.3 Lucent Technologies . 21 3.1.4 Inferno . 21 3.2 « The Unix Wars » .............................. 22 1 Chapitre 1 La gen`ese 1.1 Bell Labs Bell Telephone Company fut fond´een 1878 par le beau p`ered’Alexander Graham Bell, Gardiner Greene Hubbard. Il participa ´egalement `ala mise en place d’une soci´et´e fille nomm´eeNew England Telephone and Telegraph Company.
    [Show full text]
  • QNX® Neutrino® Realtime Operating System Photon® Microgui Programmer’S Guide
    QNX® Neutrino® Realtime Operating System Photon® microGUI Programmer’s Guide For QNX® Neutrino® 6.5.0 © 2010, QNX Software Systems GmbH & Co. KG. © 1995 – 2010, QNX Software Systems GmbH & Co. KG. All rights reserved. Published under license by: QNX Software Systems Co. 175 Terence Matthews Crescent Kanata, Ontario K2M 1W8 Canada Voice: +1 613 591-0931 Fax: +1 613 591-3579 Email: [email protected] Web: http://www.qnx.com/ Electronic edition published 2010. QNX, Neutrino, Photon, Photon microGUI, Momentics, Aviage, and related marks, names, and logos are trademarks, registered in certain jurisdictions, of QNX Software Systems GmbH & Co. KG. and are used under license by QNX Software Systems Co. All other trademarks belong to their respective owners. Contents About This Guide xxv What you’ll find in this guide xxvii Typographical conventions xxviii Note to Windows users xxix Technical support xxx 1 Introduction 1 Overview of the Photon architecture 3 Photon Application Builder (PhAB) 5 Widget concepts 6 Widget life cycle 9 Widget geometry 11 Programming paradigm 13 Text-mode application 13 Non-PhAB application 14 PhAB application 15 Photon libraries 16 API categories and libraries 16 Versions and platforms 18 Building applications with PhAB—an overview 18 Step 1: Create modules 18 Step 2: Add widgets 19 Step 3: Attach callbacks 19 Step 4: Generate code 20 Step 5: Run your application 20 Step 6: Repeat any previous step 20 Writing applications without PhAB 21 2 Tutorials 23 Before you start... 25 Creating a Photon project and starting PhAB 25 PhAB’s Interface 26 Tutorial 1 — Hello, world 27 May 13, 2010 Contents iii © 2010, QNX Software Systems GmbH & Co.
    [Show full text]
  • Download The
    THE SHIP MODEL - A NEW COMPUTATIONAL MODEL FOR DISTRIBUTED SYSTEMS By George William Phillips B. Sc. (Computer Science) University of British Columbia, 1987 A THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF SCIENCE in THE FACULTY OF GRADUATE STUDIES COMPUTER SCIENCE We accept this thesis as conforming to the required standard THE UNIVERSITY OF BRITISH COLUMBIA 1992 © George William Phillips, 1992 In presenting this thesis in partial fulfilment of the requirements for an advanced degree at the University of British Columbia, I agree that the Library shall make it freely available for reference and study. I further agree that permission for extensive copying of this thesis for scholarly purposes may be granted by the head of my department or by his or her representatives. It is understood that copying or publication of this thesis for financial gain shall not be allowed without my written permission. Computer Science The University of British Columbia 2075 Wesbrook Place Vancouver, Canada V6T 1Z1 Date: (9(2, 11i2 Abstract One of the fundamental goals of a distributed operating is to make a collection of corn— puters connected by a network appear as a unified whole to the users of the system. The system relies heavily on the network to help maintain this illusion. If the network is not fast enough system performance will be noticeably affected and the system will fail to achieve this primary goal. Since the network is used to allow two entities on different machines to communicate with each other, it is possible to reduce the use of the network by allowing entities to migrate between machines.
    [Show full text]
  • A Concurrent Window System
    A Concurrent Window System Rob Pike AT&T Bell Laboratories ABSTRACT: When implemented in a concurrent language, a window system can be concise. If its client programs connect to the window system using an interface defined in terms of communication on synchronous channels, much of the complexity of traditional event-based interfaces can be avoided. Once that interface is specified, complex interactive programs can be assembled, not monolithically, but rather by connecting, using the same techniques, small self-contained components that each imple- ment or modify elements of the interface. In partic- ular, the window system itself may be run recur- sively to implement subwindows for multiplexed applications such as multi-frle text editors. This is the software tool approach applied to windows. @ Computing Systems, Vol. 2 . No. 2 . Spring 1989 133 1. Introduction Traditional window systems offer their clients - the programs that call upon them for services an interface consisting primarily of a - o'events": graphics library and a stream of tokens representing key presses, mouse motion and so on. The clients of these systems tend to be written as state machines with transitions triggered by these events. Although this style of programming is adequate, it is uncomfortable; state machines are powerful but inconvenient. There are also engineering reasons to object to this interface style: all types of events come through the same port and must be disen- tangled; the event handlers must relinquish control to the main loop after processing an event; and the externally imposed definition of events (such as whether depressing a mouse button is the same type of event as releasing one) affects the structure of the overall program.
    [Show full text]
  • A Research UNIX Reader: Annotated Excerpts from the Programmer's
    AResearch UNIX Reader: Annotated Excerpts from the Programmer’sManual, 1971-1986 M. Douglas McIlroy ABSTRACT Selected pages from the nine research editions of the UNIX®Pro grammer’sManual illustrate the development of the system. Accompanying commentary recounts some of the needs, events, and individual contributions that shaped this evolution. 1. Introduction Since it beganatthe Computing Science Research Center of AT&T Bell Laboratories in 1969, the UNIX system has exploded in coverage, in geographic distribution and, alas, in bulk. It has brought great honor to the primary contributors, Ken Thompson and Dennis Ritchie, and has reflected respect upon many others who have built on their foundation. The story of howthe system came to be and howitgrewand prospered has been told manytimes, often embroidered almost into myth. Still, aficionados seem neverto tire of hearing about howthings were in that special circle where the system first flourished. This collection of excerpts from the nine editions of the research UNIX Programmer’sManual has been chosen to illustrate trends and some of the lively give-and-take—or at least the tangible results thereof—that shaped the system. It is a domestic study,aimed only at capturing the way things were in the system’soriginal home. To look further afield would require a tome, not a report, and possibly a more dis- passionate scholar,not an intimate participant. The rawreadings are supplemented by my own recollec- tions as corrected by the memories of colleagues. The collection emphasizes development up to the Seventh Edition (v7*) in 1979, providing only occasional peeks ahead to v8 and v9.
    [Show full text]
  • Dash1.Nothinkpad.Pdf
    '.4ON6 .4-37-N6L; 37-561ON-, )N59-45 6DEI >ook M=I JOFAIAJ troff -ms -mpictures|lp -dstdout|ps2pdf En LK?E@= 5=nI >OJDA=KJDoH,KIEnC=LAnoLo6DEnk2=@: HKnnEnCJDA'BHonJoFAH=JEnCIOIJAm. 4An@AHA@: -#- # '.4ON6 'BHonJ.oHC 15*N-!:'%&$'%$''&"# 6DEI EI = MoHk oB BE?JEon. N=mAI, ?D=H=?JAHI, Fl=?AI =n@ En?E@AnJI AEJDAH =HA JDA FHo@K?J oB JDA =KJDoHߣI Em=CEn=JEon oH =HA KIA@ BE?JEJEoKIlO, =n@ =nO HAIAm>l=n?A Jo =?JK=l FAH­ IonI, lELEnC oH @A=@, >KIEnAIIAI, ?omF=nEAI, ALAnJI oH lo?=lAI EI AnJEHAlO ?oEn?E@AnJ=l. 4E?D=H@ MEllAH =n@ 5JALA 5J=llEon =HA noJ =BBElE=JA@ MEJD 'BHonJ. 6DA oFAH=JEnC IOIJAm @oAInoJD=LA=noBBE?E=lFoHJIJHAA. M16/++/2K>lE?,om=En The study of this Book is forbidden. It is wise to destroy this copy after the first reading. Whosoever disregards this does so at his own risk and peril. These are most dire. Those who discuss the contents of this Book are to be shunned by all, as centres of pestilence. All questions of the Law are to be decided only by appeal to my writings, each for himself. There is no law beyond Do what thou wilt. 9FRONT FREQUENTLY QUESTIONED ANSWERS ACHTUNG! 'BHonJ@=IDm=nK=lEIMHEJJAn>O=n@BoH'BHonJKIAHI. Those who can do, those who can’t write and those who can’t write make ezines. ߞ 5=FAMKllAn@AH ACHTUNG! 1nBoHm=JEon FHoLE@A@ >O JDEI @o?KmAnJ EI 7NO..1+1)L =n@ m=O >A oKJ@=JA@ oHjKIJFl=En94ON/.7IAOoKH>H=En.NO4-.7N,5.
    [Show full text]
  • The Unix Magician's Handbook
    The Unix Magician’s Handbook Gerard J. Holzmann° Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT A review of "The Unix Programming Environment," by Brian W. Kernighan and Robert Pike, Prentice-Hall Software Series (1984), ISBN 0-13-937699-2. Unix:Login, 1984, (publisher under the name Elizabeth Bimmler) The Unix Wizard Unix† is traditionally taught by ‘wizards.’ Every installation, and there seem to be well over 3000 now, inevitably comes with its own set of gurus where Unix freshmen can learn the art of Unix programming. Until recently, the prospective Unix programmer had to find a guru and seek to become his apprentice. After a long training the student could then become a master and as a token of his excellence would be issued the superuser password. Unix, to be sure, is not a trivial system, and as Kernighan and Pike note in the preface to their book: "as the Unix system has spread, the fraction of its users who are skilled in its application has decreased." The Unix operating system has been acclaimed for its conciseness and structure, its portability, and perhaps more important still: for its availability. Commenting on the 6th Edition Unix, John Lions made the follow- ing, often quoted, observation: "the whole documentation is not unreasonably transportable in a student’s briefcase." As Kernighan and Pike hav eaptly countered in their book: "this has been fixed in recent ver- sions." Considering that the kernel of the first edition Unix was only 8k in size, on the average, the size of the system has more than doubled with every new edition issued.
    [Show full text]
  • Window Systems Should Be Transparent Rob Pike AT&T Bell Laboratories
    CONTROVERSY Window Systems Should Be Transparent Rob Pike AT&T Bell Laboratories ABSTRACT: Commercial UNIX window systems are unsatisfactory. Because they are cumbersome and complicated, they are unsuitable companions for an operating system that is appreciated for its technical elegance. Their clumsy user interfaces clutter the view of the operating system. A good interface should clarify the view, not obscure ít. Mux is one window system that is popular and therefore worth studying as an example of good design. (It is not commercially important because it runs only on obsolete hardware.) This paper vses mux as a case study to illustrate some principles that can help keep a user interface simple, comfortable, and unobtrusive. When designing their products, the purveyors of commercial window systems should keep these principles in mind. I. Introduction Mux is a window system with no icons, no help facility, no cus- tomizability, no noise, and only two menus (one with frve entries, one with seven). The spareness of its user interface distinguishes it from commercial window systems such as X and SunVy'indows, yef mux is a comfortable and effective system. As the author of mux,l am told by many people who have tried other window @ Computing Systems, Vol. I 'No. 3 'Summer 1988 279 systems thaf mux is preferable. Why is a window system that is so simple also so popular? The task of a window system is to provide a multiplexed inter- face to an operating system. 'Windows' is an apt word because it is through windows that we see the operating system and its pro- grams.
    [Show full text]