MPW 3.0A2 Release Notes July 14, 1988 Overview This release note pertains to the following MPW products: • MPW Development Environment • MPWPascal •MPWC • MPW Assembler MPW C++ has its own separate release note. This release note, the MPW 3.0 ERS's, and other tool-specific release notes are the documentation for this release. Differences between the ERS, previous 3.0 development releases, and this release are documented below. If no release note exists for something that has an ERS, assume that the piece has been implemented as documented in the ERS. MPW 3.0A2 highlights include a symbolic debugger, project management system, and new C compiler. All of the C pieces of MPW, were compiled with this new C. Since MPW 2.0, the C header files have three important changes: every function has a function prototype, the capitalization for routines that pass strings and points has changed, and the definition of Str255 has changed. The capitalization and Str255 changes will require changes to your C source. See the section below titled ''Interfaces." Another change in MPW 3.0A2 may require a change to your Makefiles. The Pascal compiler no longer uses the Load/Dump mechanism. Instead, the compiled object code for each unit is saved in the unit's resource fork. Therefore, dependency rules (in Makefiles) upon Pascal dump files are obsolete. See the section below titled ''Pascal." The A2 C compiler now has function prototype checking turned on. Furthermore, the C compiler is very strict about type compatibility. Be forewarned ... Installation • Installation horn floppies - MPW 3.0 now includes an installer disk for installing MPW from a set of floppy disks. Here are the steps for automatically installing MPW on your disk: 1) drag the "Installation Folder" onto the hard disk where you want MPW installed 2) launch the MPW Shell found in the ''Installation Folder" Apple Computer, Inc. Confidential Page 1 (the one you just dragged onto your hard disk) 3) the installation script will run and will prompt you to insert a disk in the internal drive. You can insert the MPW disks in any order and it won't hurt to insert a disk more than once. …

030-3626-A MPW 3.2 Assembler Release Notes The following features have been added to the Assembler for version 3.2. • New optimizations. • Longer identifiers. • New parameter and syntax for module directives. • MC68040 support. • "32-Bit Everything" support. • Improved SADE support. • A new macro function : &SYSINMOD New Optimizations The 3.2 Assembler supports optimization of instructions which were previously not opti- mized. The following additional optimizations are available: ADD #<Data>,An [-8 <= data <= -1) =====> SUBQ #-<Data>,An ADDA #<Data>,An [-8 <= data <= -1] =====> SUBQ #-<Data>,An ADDI #<Data>,An [-8 <= data <= -1) =====> SUBQ #-<Data>,An SUB #<Data>,An [-8 <= data <= -1] =====> ADDQ #-<Data>,An SUBA #<Data>,An [-8 <= data <= -1] =====> ADDQ #-<Data>,An SUBI #<Data>,An [-8 <= data <= -1] =====> ADDQ #-<Data>,An The above optimizations only occur when the Assembler understands the operand to be a negative number. Since the Assembler operates on 32-bit arithmetic, the value of the operand must be written as a negative number in order to activate the optimization. Tiris is necessary regardless of the size (B, W, L) of the instruction. Thus, in a byte operation, the operand must specify "-1" instead of "$FF". even though, un-optimized, they would both compile to the same instruction. MPW 3.2 Assembler 1 Copyright Apple Computer, Inc. Release Notes 1990-1991. All rights reserved. ADDI #<Data>,<EA3> [+l <= data <= +8] =====> ADDQ #<Data>,<EA3> SUBI #<Data>,<EA3> [+l <= data <= +8] =====> SUBQ #<Data>,<EA3> ADD.I #<data>,An [-32767 <= data <= +32767] =====> LEA <Data>(An),An Longer Identifiers The Assembler now suppons identifiers of lengths up to 251 characters (this was done primarily to support C++ name mangling). On detecting a name that exceeds this maxi- mum, the Assembler issues the warning: ID longer than maximum length ... truncating to maximum length. New Parameter and Syntax for Module Directives A new parameter, ForceActi ve, exists for the ccxie module and data mcxiule directives. A new syntax has been provided and error checking for conflicting parameters is in effect. ForceActive ForceActive causes a ccxie or data module to be included in the final linked output even if the Linker would otherwise strip that code or data module because there were no refer- ences to it. Syntax For code module directives: Line ::= [label] CodeDir [KeywordList] CodeDir ::= PROC I FUNC I MAIN KeywordList ::=Keyword I KeywordList, Keyword Keyword::= ENTR…

030-3621-A MPW3.2 Release Notes Erratum Due to an oversight, an erroneous comment symbol was used in lines 20 through 24 of the source file: {MPW}PExamples:TESampleGlue.a The character"#" was incorrectly written where the character";" should have been written. MPW3.2 i Copyright Apple Computer, Inc. Release Notes 1990-1991. All rights reserved. MPW3.2 Release Notes This release note summarizes the differences between MPW 3.2 and MPW 3.0, the last version for which a reference manual exists. Details beyond those given in this note are to be found in separate release notes entitled MPW 3.2 Shell, MPW 3.2 Object Pascal, MPW 3.2 C, MPW 3.2 Assembler, MPW 3.2 Libraries & Interfaces, MPW 3.2 "411" Help, MPW 3.2 Run-Time Architecture, MPW 3.2 SIOW, and MPW 3.2 Tools & Scripts. Three of the above: "411" Help, Run-Time Architecture, and SIOW describe completely new features. Principal Changes Shell • Projector has a number of enhancements. • The Editor provides split windows. • A marker browser has been provided. • There are additional commands for the faccess function. • The save command, when scripted, saves the resource fork of a file if any resource has changed. • MPW can now be run under A/UX. • New System 7 .0 error codes have been added to the file SysErrs.err. c • A variety of new object code optimizations have been implemented. • There are new compiler options to control optimization level. MPW3.2 1 Copyright Apple Computer, Inc. Release Notes 1990-1991. All rights reserved. • Support is provided for the MacApp debugger and code profilers (generating a preamble and postamble for functions). • A new pragma is provided for passing parameters to functions via registers. • A new pragma is provided to force the generation of MC68020 code. • A new pragma is provided to prevent the multiple inclusion of header files. • There is a new option for invoking the "32-bit everything'' run-time architecture. • A new pragma is provided to prevent dead code stripping by the linker. • An option is provided for machines having the MC68020 and up that allows stand-alone code segments greater than 32K. Object Pascal • Further object code optimizations, including an optional two-pass code generation phase which allocates unused scratch registers for local data. • An option to control optimization level. • An option for invoking the "32-bit everything'' run-time architecture. • A new syntax for declaring forward and external objects • Enhancements to the Object Pascal declaration handling to support MacApp. • Support for USES clauses in the implementation section of a unit. • Support for external C functions with arbitrary numbers of…

® Macintosh®Programmer's Workshop Toolbox Interfaces and Libraries Version 7.0 M0615LUB 030-B0 16-A 030-3622-A MPW 3.2 Libraries/Interfaces Release Notes Libraries Changes to the libraries since MPW 3.0 include the elimination of CInterface.o and CRuntime.o, their functionality having been merged into Interface.o and Runtime.o. The libraries have been resegmented so as to reduce the number of modules in segment "main". The MPW 3.2 C libraries conform to the current ANSI C standard. A number of modifi- cations and additions have been made to the set of library functions, including new C-like string functions for Pascal strings and a C function for setting the type and creator on any file. A new library provides for the creating of applications that use a simple text I/O win- dow to display and read console I/O (SlOW). For details, see the MPW 3.2 Simple Input/Output Window Release Notes. Linking Requirements The library CLib881.0 has a new positioning requirement as a consequence of the elimina- tion of CRuntime.o. CLib881.0 must now not only precede all members of {CLibraries} in the link sequence but must also precede the library Runtime.o. Note that XCMDs for Hypercard require linking into one segment. Because of the new segmentation of the library, this will no longer happen automatically. This requirement can be met by putting the option -sg main on the link: command line to force the library rou- tines and your code into a single segment. MPW 3.2 LibrarieslInterfaces 1 Copyright Apple Computer, Inc. Release Notes 1990-1991. All rights reserved. Segmentation The libraries have been resegmented, moving many of the modules out of the segment "Main". The goal of changing the segmentation is to minimize the number of modules in the segment "Main". This way, if the user needs the space in "Main" for his application or tool, he has it. If he is more concerned about speed, the user can then manipulate his makefile to contain whatever he needs in his "Main" segment. • Segment layout LIBRARY Runtlme.o Se&ment Contents MAIN Initialization and exit procedures, 32 bit math operations %A5Init A5 initialization code, _DataInit, Module #000 1 INTENV Low level IOPort functions and I/O which directly calls those functions - done for pc relative offsets SADEV Device drivers <.S.tand Alone Devices) LIBRARY Pasllb.o SelWlent Contents MAIN Compiler initializations (the functions call Runtime.o) INTENV I/O which directly calls segment INTENV in Runtime.o (may change in the future) SIDIO Pascal language I/O PASLIB Heap, strings and math functions LIBRARY StdCLlb.o …

MPW 68K Object File Format 11/5/96 Introduction ....................................................................................................................................... 3 Code Records ........................................................................................................................ 3 Definitions................................................................................................................. 4 Symbolic Records ................................................................................................................. 5 Scoping of Symbolic Information ............................................................................. 5 ModuleBegin Implementation/Declaration Semantics ............................................. 7 Object File Records........................................................................................................................... 7 Pad Record ............................................................................................................................ 8 First Record ........................................................................................................................... 9 Last Record ........................................................................................................................... 9 Comment Record .................................................................................................................. 10 Dictionary Record ................................................................................................................. 10 Module Record...................................................................................................................... 11 EntryPoint Record ................................................................................................................. 12 Size Record ........................................................................................................................... 13 Contents Record .................................................................................................................... 13 Reference Record .................................................................................................................. 14 ComputedReference Record ................................................................................................. 19 Filename Record ................................................................................................................... 19 SourceStatement Record ....................................................................................................... 20 ModuleBegin Record ............................................................................................................ 21 …

4. '• Macintosh Programmer's Workshop AS Driver Runtime Library Writing a Desk Accessory or Device Driver that Uses Global Data. Steve Hartwell June 12, 1986 Revised July 30, 1986 Notice: This documents the ASDRVRRuntime.o library, which is not released with MPW 1.0. For information about writing desk accessories or drivers which don't need global data, use the DRVRRuntime.o library provided with the MPW 1.0 release, and see the MPW manual section on " Writing a Desk Accessory or Other Driver Resource". The A5DRVRRuntime.o library is available internally to Apple engineers; contact the Development Systems Group for more information. Overview. Desk accessories and other drivers have traditionally been written in assembly language, partly because of the peculiar format of the 'DRVR' resource needed for drivers. Setting up the DRVR layout header, passing register-based procedure parameters, and coping with the nonstandard exit conventions of the driver routines has made it fairly difficult to implement drivers in higher-level languages like Pascal or C. The library ASDRVRRuntime.o and the resource type 'DRVW' declared in MPWTypes.r simplifies the task of writing a desk accessory or device driver in Pascal or C. Together they compose the driver layout header and the five entry points which set up the open, prime, status, control, and close functions of a driver. The advantages of using A5DRVRRuntime.o are: • No assembler source is required. • The resource compiler is an integral step in the build process, permitting the easy addition of a desk accessory menu or other owned resources. • The programmer's interface to the open, prime, status, control, and close routines use Pascal calling conventions. Since the C compiler can easily be directed to declare functions which use Pascal calling conventions, the driver header can by used by both languages without additional glue. Each function returns a result code which is passed back to the system. • Previously, desk accessories and drivers have been required to allocate their own storage for global data. A5DRVRRuntime uses the new A5Lib routines which allow access to initialized global data as the languages and assembler support them. • Because access to global data is available, drivers may link with the language libraries, including routines which reference global data (but see note below}. A5DRVRRuntime Library Internal Release Only …

 Macintosh Macintosh Programmer’s Workshop 3.0 Assembler Reference APPLE COMPUTER , I NC. This manual and the MPW, QuickDraw, ResEdit, MPW sample programs software described in it are APDA, and SADE are Apple Computer, Inc. grants copyrighted, with all rights trademarks of users of the Macintosh reserved. Under the Apple Computer, Inc. Programmer’s Workshop a copyright laws, this manual royalty-free license to or the software may not be MacDraw, MacPaint, and incorporate Macintosh copied, in whole or part, MacWrite are registered Programmer’s Workshop without written consent of trademarks of sample programs into their Apple, except in the normal Claris Corporation. own programs, or to modify use of the software or to make the sample programs for use Microsoft Word is a a backup copy of the in their own programs, trademark of the Microsoft software. The same provided such use is Corporation. proprietary and copyright exclusively on Apple notices must be affixed to any computers. For any modified permitted copies as were Motorola is a trademark of Macintosh Programmer’s affixed to the original. This Motorola, Inc. Workshop sample program, exception does not allow you may add your own copies to be made for others, MathType is a trademark of copyright notice alongside whether or not sold, but all of Design Science, Inc. the Apple copyright notice. the material purchased (with all backup copies) may ITC Garamond and ITC Zapf be sold, given, or loaned to Dingbats are registered another person. Under the trademarks of International law, copying includes Typeface Corporation. translating into another POST S CRIPT is a registered language or format. trademark of Adobe Systems You may use the software on Incorporated. any computer owned by you, Adobe Illustrator 88 is a but extra copies cannot be trademark of Adobe Systems made for this purpose. Incorporated. © 1985, 1986, 1987, 1988 ImageStudio is a trademark of Apple Computer, Inc. Esselte Pendaflex Corporation 20525 Mariani Ave. in the United States, of Cupertino, Cali…

MPj Astro 1.5.1 Instruction Manual Introduction Welcome to Microprojects’ MPj Astro, astronomy programme for the Apple Macintosh. This instruction manual is your guide to MPj Astro and all of its features. For the most part, the topics in this manual are organized by MPj Astro’s main dialogues, menu titles and each item in those menus. Read the section called “Setup Dialogue” first. This section will tell you what you need to do to have MPj Astro display the night sky as seen from your location and remember those settings. From there, you are free to experiment and try out all the features, menu items and controls. You will probably want to read through this manual in its entirety at some point. That way you can get a better understanding of the variety of features available and learn what methods best suit you to use this application. Help balloons are available for all menu items, the main dialogues and display features. Microprojects hopes that you have many hours of enjoyment , discovery and learning about astronomy with MPj Astro. PLEASE SUPPORT SHAREWARE Go to Registration Page MPj Astro Manual Introduction Page 1 Installation Shareware Installer To install MPj Astro on your hard disk simply double-click on the MPj Astro Installer icon. You will be asked where you want to install the programme and then several files will be uncompressed and placed in a folder named Microprojects. The installer remains unaltered after the installation. Once installed, the Microprojects folder should contain the MPj Astro application, a READ ME file, four data documents, a shortcuts file in the AstroText folder and this manual. The best version (68k, fpu, ppc) of MPj Astro for your computer will be automatically installed. Registration Installer This installer contains 35 high resolution astronomy photographs and the AstroStar document which contains data on all 7th and 8th magnitude stars (~65k stars). If you have a registered version of MPj Astro 1.4, 1.4.1 or 1.5, you can upgrade to version 1.5.1 at no cost. See the MPj READ ME file for information. Launching MPj Astro You launch MPj Astro like any other Macintosh application. You can select the MPj Astro icon and chose Open from the Finder menu or you can double click on the icon. You can also double click on any MPj Astro document although these documents are not available to you to be changed in any way. You can also create an alias of MPj Astro, place it anywhere you like, and launch from the alias. A registration dialogue will appear the first time you launch MPj Astro after using the registration installer. Please enter your name where indicated. This will register you as the user of your copy of MPj Astro and your name will appear in the start-up display each time you launch MPj Astro. If you ever have to change the registered name, hold down the option key as you launch MPj Astro and the…

MRJ Minimal Webserver This application demonstrates the power of Java and of Macintosh Runtime for Java (MRJ) - Apple's implementation of the Java virtual machine for MacOS. In less than 600 lines of source code (including comments and whitespace), or less than 32Kb of object code you get a working, multithreaded webserver. All this packaged as a standalone, double- clickable MacOS application that that looks and feels as it should. [About the WebServer | About MRJ | System Requirements | Running the WebServer | Troubleshooting | Source Code ] System Requirements MRJ 1.02 (comes with MacOS 8), but preferably MRJ 1.5 you can download either from http://applejava.apple.com active TCP/IP at least enable TCP/IP and give your machine a IP address Running the WebServer With MRJ installed on your MacOS computer, double-click the program icon named 'MRJ Minimal WebServer', give it some time to come up (due to heavy usage of multithreading, the user-interface comes up a bit slow). If all is well, you see the message 'WebServer started.', otherwise some error condition occured and a message will be printed in the console transcript window. Use a browser on your own or on another machine on the same TCP/IP network to connect to the web server by typing its IP address in the location field. If you are on the same machine, you can also type the localhost address 127.0.0.1. Have fun! Troubleshooting If the web server did not start up as it should, it printed an error message in the console transcript window instead of the message 'WebServer started.'. In almost all cases the error will be related to the fact that TCP/IP is not started up correctly - double check this using the TCP/IP control panel. Source Code You can download the full source code of the MRJ Minimal WebServer as a MetroWerks CodeWarrior Pro 1 MacOS project from http://www.ping.be/BetaNine. Based on code by David Brown of the Java Developers Connection. Written by Sven Van Caekenberghe of Beta Nine.