(

rrlie Sourcerors 5ZLpprentice"

The Assembly Language Journal of Merlin Programmers Vol. 1 NO.7 July, 1989

Apple, Inc. Left •In KC DustNormally, the mission of The Sourceror'sApprentice is to provide source code examplesto y'all. It's that simple.

Due to the vast importance and significance ofthe A2-Central Developer's Conference inKansas City, however, I'm going to deviatefrom the norm (more than usual) and delveinto the world of editorial. Bear with me. Wehave source code for you this month, too, but Iknow that most of you are intensely interestedin the II, and I think you'll want the straightskinny as reported and interpreted by anotherdeveloper.

So here we go.

Some of the events of most obvious import tome were not on the schedule. No one scheduledBarney Stone's passionate rebuke of Apple,Inc. marketing strategy. No one scheduledApple employee Eric Soldan's delivery ofApp.Builder, his macro-based assemblylanguage environment for 8 bit Apples. No onescheduled the formation of the Apple IIDevelopers Association, an event of historicalimportance. And no one scheduled BillMensch's radical support of his 65XXX series ofchips - an impromptu pledge of megabuckventure capital support for languagedevelopment on the IIgs.

It was a very interesting conference.

Contrary to what many of you predicted,Apple, Inc. sent lots of people, over 20 if Iremember correctly. The only unfortunateevent of the weekend was the vitriolicoutbursts directed at Apple, Inc. marketingthat had to be fielded by the Apple employeespresent. It was a little like killing themessenger. The Apple folks present were therebecause they love the II. I found them to bequite supportive, incredibly knowledgeable,and very patient. Apple done good by hiringDave Lyons, Matt Deatherage, Eric Soldan,Jim Mensch, Tim Swihart, and the rest of thegang.

I think Apple, Inc. was left in the dust and

outclassed by its own employees. LaserComputers, Beagle Bros., and of course, the A2­Central people (thanks, Tom Weishaar). Yes,there is a little momentum building for the IIat Apple (especially on the technical side ofthings - System 5.0 is GREAT, the overlay cardis hot, App.Builder will save us tons ofdevelopment time, etc.), but until the companycan figure out and execute a viable marketingstrategy, Apple II sales will shrink (at worst) orremain static (at best). I am pleased that Appleseems to be making good on John Sculley'spromises at the last San Francisco AppleFest.Apple's Apple II employees are doing wonderfulthings. But what is it going to take to get themarketing department in line? I cannotbelieve that John Sculley is willingly allowinga billion dollar profit center to dribble awaybecause the marketing boys are feeding him adistorted view of the market. I could get excitedabout any serious ad campaign for the II, but Iwant ads revealing the II series as the fantasticgeneral purpose computer that it is. I wantdealers who support the II in the manner itdeserves. I want a coherent strategy which pHsthe II and AppleWorks against the IBM clones,not the Mac. Since Apple saddled the IIgs withthe desktop interface, I would very much liketo see an ad touting that interface on the II! Iwant a strategy which understands theimportance of color and cost effectiveness ineducational 'computing. I want somemarketing that is based on reality, notprejudice.

rrfie Sourceror '.s .f2Lpprentice Vol. 1 NO.7 Page 2

Well, I'm grateful to get that out of my system.But I have one last word: Will someone(anyone?) in Apple marketing stand up and becounted? Explain to us your rationale, yourplan. As a student of marketing myself (I gavea seminar on it at the conference), I can onlyconclude that Apple II marketing is wanderingin the wilderness.

Here were some of the highlights of theconference that are most likely to be of interestor concern to Apprentice subscribers:

• The Beagle Boys really did tell all aboutAppleWorks and TimeOut internal routinesand structures. They gave us the tools (and theencouragement) to develop TimeOutcompatible applications for them to publish orfor us to publish ourselves (for a 4% royalty, amost reasonable fee, I'd say). You won't readany details within our pages however;everyone present had to sign a non-disclosureagreement. I doubt the opportunity to get atthis data will come around again (at least untilnext conference). If the Beagle Bros. offer thisagain, I cannot over-encourage you to beinvolved.

• Laser Computers wowed the crowd with somefantastic hardware (the EX2 will be shipping inmid-August) and fantastic support fordevelopers. Not only do they have a hardwarepurchase program for commercial developers(there is no fee for the developer program,either), but they also announced a developerco-marketing project. This venture is simplywonderful; if you can produce a four color adand submit it to them by September 11th, theywill reproduce the thing free in a catalog thatgoes out with every single Laser computer.Since they ship 12,000 per month, that isnothing to sneeze at. As the Laser reps said,'We're young and we're hungry." Contact MikeWagner at (312) 540-8086, extension 744. Ohyeah, your software must be Laser compatible,but that is not an obstacle. The Laser boyshave a semi-confidential list of ROM entrypoints they support which is free for theasking.

• Apple announced an updated BASIC.SYSTEM1.3 which should be immedia~ely ditched.They have had unfortunate luck with anysoftware with those numbers (rememberProDOS 1.3?). They forgot an RTS in a routinethis time, allowing the code to fall through aREAD routine into a WRITE routine. DON'TUSE BASIC.SYSTEM 1.3!!! An immediate

update is forthcoming, of course. I guess I don'tfeel quite so bad about my own silly boo boosnow!

• Chris Haun was showing off a version ofDesignMaster compatible with System Version5.0. It was a ridiculously wonderful package,and vastly underpriced. This is a full featuredpiece of prototyping software that producesyour entire desktop interface includingWindows, text, buttons, lists, pop-up menus,and much, much more. This package is so nicethat we here at the Ariel Cabin are going to buycopies in bulk and sell them to you like adealer. I plan to sell the 5.0 version for $28(including shipping), so you should be able toget your hands on a powerful productiVity toolat a remarkable price. Prototyping software isall the rage on other computers because it helpsyou to program faster and better. If you dodesktop programming of ANY kind on the GS,this package is a MUST HAVE. And don'tforget that I said those things even before westarted selling the software. I hope our priceconvinces you of our commitment to gettingthe product into your hands.

There were many, many other valuable andenjoyable aspects of the conference. MeetingBob Sander-Cederlof in person was a joy, aswas a chance to really talk with BrianFitzgerald and John Brooks (two of thecleverest programmers in this plane ofexistence). Their contributions to EricMueller's animation seminar were terrific.

And that certainly wasn't all. I havementioned App.Builder twice now and notexplained it thoroughly. The long and theshort of it is that Eric of DTS put together anincredibly powerful set of macros that make 8­bit assembly language programming a lot likeworking in a higher level language. Since themacros are VERY intelligent. the code theygenerate is qliite clean and lean. The onlydrawback is that. due to a bug in APW macroparsing routines, the only working version isfor the MPW cross-development system. Ericcut me a deal, though, and this is what wegonna do. I'm going to translate his work toMerlin format, hence I think it'll be operativeon Merlin before APW!!! There is somethingironic about that ... I don't know how long thetranslation will take, but when we are finishedwe'll make it available to you absolutely free ofcharge (assuming you provide a self-addressed,stamped envelope and a disk). Let me stressthat App.Builder is a productiVity tool, too,

Vol. 1 NO.7 Page 3 %e Sourcerors .9Lpprentice

and it will make your work faster and easier.

I am exuberant and excited, but I have one lastprophetic warning. Momentum is building forthe II again, thankfully, but Apple has yet toreap all the consequences of years of neglectand exploitation. Computer markets turnslowly nowadays, and Apple's moderateamount of support at present will not stem thetide in the short term. The die has alreadybeen cast, if you'll forgive mixed metaphors,and some very nasty things will happen in thenext year to 18 months. I think there will be

profits for those able to persevere. But we mustlobby Apple like maniacs to insure that theypersevere as well.

Oh yeah, the KC Royals game was fun, too. Bowent 3 for 4, but the good guys lost.

On a non-conference note, we here at the ArielCabin are so impressed with AppliedIngenuity's hard drives (combined with theircompetitive pricing), we have asked to becomea dealer. We've included a price list. And youthought you couldn't afford a hard drive!

Making a List(and checking it twice!)

By Ross W. Lambert, Editor

I was tempted to hold this article until Christmas just so the headline would be timely.Fortunately, I have a little bit of a Christmas present for you, anyway: the Apple ngs™ ListManager is easier to use than I imagined.

Although the Toolbox References are cryptic and ambiguous regarding the List Manager, andalthough Gary Little calls it rarely used (Exploring the Apple JIgs, p. 194), and although theApple IIGS Source Code Sampler confounds the issue with extraneous code (take a lesson fromeducators, DTS, one major point per lesson), I was pleasantly surprised to discover that theList Manager is a friendly sort of beastie.

The List Manager's utility stems from its fleXibility. Imagine a situation wherein users arereqUired to make selections from a constantly and Widely varying list (maybe based onproduct availability or some such changeable thing). It's a nightmare to program and fom1atif you attempt to convert the items to buttons or other controls, and a nightmare to use if youdon't ('What was the name of that item, again?").

The List Manager, however, handles these situations with ease. In fact, every time you useSFGetFile, the scrolling list of files is coordinated by the List Manager and its co-authority,the Control Manager.

Using the List Manager in its wildest permutations can get a little hairy (it can handle lists ofgraphical objects as well as textual lists), but in its plain vanilla form the animal is quitetame. We shall examine but one simple application of lists. Fortunately, the simplest is alsothe most common.

As is the usual case with toolbox routines, one of the most difficult tasks is seLling up theassociated data records. There are three discrete structures reqUired by the List Manager, thelist record, the item records (also called member records), and the item strings themselves.

Here's what the "List Record" looks like for one of my lists:

%e SourcerorS.J2lpprentice

ListRecord

Vol. 1 No.7 Page 4

PADADADADAADRLADRLDADAADRLADRLADRL

30,30,102,230listSizelistviewlistTypelistStart$0000$0000listMemHeightlistMemSizeMyList$0000$0000

iRECT in which list should fititotal number of items in listitotal items in sight at onceibits 0 & 1 flag parmsifirst member to highlightihandle to list controlidrawing routine (0 = default)iheight of list members in pixelsisize of member's data recordiPointer to member dataifour bytes for application useiscroll bar color table (0 = default)

Most of the data is pretty straightfolWard. but a few items beg explanation. The item listTypehas two bit-sized flags. each of which controls something about the list. Bit zero flags the typeof string in use. A zero tells Mr. List Manager that you want to use Pascal strings (which have aleading length byte). A one says. "Hey. I want C strings!". which, of course, end with a $00terminator.

Bit one flags the type of selection allowed. Unlike SFGetFile, programmer designed lists inaypermit selection of a range of items and/or multiple unconnected items. Setting bit one to aone permits single item selection only, while a zero permits the range type of selection rules.All of the other 14 bits must be set to zero. See p. 11-12 of Toolbox Reference Manual, VolumeOne for more information.

Figure 1. listType selection flags

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

)_ reserved and - 0 . . ~

o Multiple/range selection1 = Single selection mode

o Pascal strings1 = C strings

The listStart field merely determines the number of the item that you want to appear at thetop ofthe list. This is normally item one, although ifyou want the user's last choice at the top,you could do it that way. too.

The item commented as the "handle to the list control" is really just space prOVided for the ListManager to fill in. I do not make any use of this handle at present.

listMemHeight is simply the height of the font used to display the list. If you're using thesystem font. plop in a 10. On a related note, you'll notice in my RECT dimensions that theheight of my list is defined to be equal to listView * listMemHeight+2, or 7 * 10 + 2 which is72. The plus two snuck in there so that the last item in the window does not rest on the line atthe bottom of the list; it is purely aesthetic.

The listMemSize parameter refers to size of the item record you have provided for each itemin the list. More on that in a minute. '

Vol. 1 NO.7 Page 5 rrfie Sourcerors .!lLpprentice

MyList is a pointer to the item records Ijust referred to. Let's look at it:

* Item Records

MyList

ADRL Item1DFB 0ADRL Item2DFB 0ADRL Item3DFB 0

* String data

Item:\. str 'Item number 1 'Item2 str 'Item number 2 'Item3 str 'Item number 3 '

icontains address of stringirequired flag byte

iand so on up to liitSize ...

listMemSize in our case would be five, this because each item record has a long pointer (4bytes) to the associated string, and a required one byte flag for use by Mr. List Manager. Five istherefore the smallest possible item record. You may make each item record larger if youwant. S0r:r;te folks tuck in little flags for their own use.

.As you can see, setting up a list 'tain't no big deal. You can even read in your data from disk orslide it in from a resource (a new feature in System 5.0 - Don't fret, we'll get to them soonenough).

Creating a list is also pretty tame stuff. Here's a fragment from a program I just finished:

iheight of system fontiPointer to string + memFlag

iresult space

3010230230

phaphaPushLong W1PtrPushLong #ListRecordCreateList

PullLong ListHandle

listYtoplistYbotlistXtoplistXbot

585 **************************************************586 * *587 * Setup List Manager Stuff *588 * *589 **************************************************590591 SetupList592593 listSize 16594 listview 7595 listType %00000010 imultiple and range selection

allowed, Pascal strings (leading len byte)596 listStart = 1597 listMemHeight = 10598 listMemSize 5

byte599600601602603604605606607608609

rrtie Sourcerors flLpprentice Vol. 1 No.7 Page 6

610611 RTS612613 ListHandle614 ADRL $0000

Creating a list is really just a matter of pushing a long result space, passing a window pointerand the address of your list record, and then calling _CreateList. Keep in mind, however, that_CreateList just arranges memory. Nothing is displayed on screen yet.

Which brings me to my next point: the List Manager works hand in hand with the ControlManager. In fact, a list is really a complicated set of controls. Therefore the mechanism toreveal an existing list is simply to call_DrawControls.

The question remains, though, when do you call_DrawControls .? The answer is: it depends.Since I use TaskMaster most of the time, I draw the controls in the routine TaskMaster calls tofill in the content of my window. Note that if you try to draw a list that does not exist yourprogram will die!

Here's a snippet:

~MoveTo #15i#15~DrawString #MsgAddr

PushLong W1PtrDrawControls

DrawContent

MsgAddr str

iand program bankimust end with RTL!

irefresh controls

ipush TM's data bank on stackipush current program bankipull back to make data bank = prog

ifirst pass?inopeiyep, so set flag

'Here is a list for you to play with:'

PrintSelection

ListFlag:contListFlag:cont2

jsr

phbphkplb

ldabnedecjmp

:cont

:cont2

drawout plbrtl

755756757758759

bank760761762763764765766767768769770771772773774775776777778

You probably noticed the JSR PrintSelection in line 769. I'll tell you more about thatroutine in a few paragraphs.

Now that the Control Manager has displayed our list, we must figure out how to operatethe thing. This is our Christmas present, however; the Control Manager already knowswhat to do!

Using TaskMaster's event code, I branch to my routine that handles a mouse down inthe content area of a window. Once there we find and track a control (which we have todo whenever there's a control in a window), and if the user selects an item, handle the

Vol. 1 NO.7 Page 7 %e Sourcerors .9l.pprentice

selection (you don't even have to do that much). By the way, the fragment belowassumes that our list is the only control in the window. If you need to check for a hit inthe list (as opposed to a button or some other control), the Control Manager "part code"for a list is $88.

exit rts

pha iresult spacePushLong #FControlHandlePushLong EventWherePushLong W1PtrFindControl

onControl PHA ipush it back on stackPushLong EventWhere iand position-via TaskMaster's recordsPushLong #-1 idefault action procPushLong FControlHandle iand handle to found control_TrackControl itrack the buggerPLA istill on a control?

ifind out if we clicked on a control

iif so, tell us what we picked

iif not, leaveiCMP $88 here if you need to distinguish

isave TM's databankipush prog bankipull down into data bank register

exit

PrintSelection

beq

plbrts

jsr

PLA iA has code for control clicked in if anyBNE onControl

from other controlsphbphkplb

InContent158159160161162163164165166167168169170171172173174175176177178179list180181182183184185186187188

As I mentioned earlier, you don't really need to handle item selections until the user isall done with the list. The dynamic duo (the List Manager and the Control Manager)will keep track of what is selected and what is not. In my examples, I wanted to let theuser know what item has just been selected (redundant, since it is highlighted in thelist, but it is to prove a point).

The point I'm talking about is the technique for determining which item is selected.

The _NextMember call does this job. The only tricks involved are to push a long wordresult space, the number of the item to start searching with, and the address of the listrecord (see lines 797-801 below). NextMember searches the list from the item numberyou provide to the end of the list. -If it finds a selected item, it returns a pointer to theitem record (also called a member record) of the next selected member found.

790791792793794795

PrintSelection

phdida DPAddrtcd

isave TM's direct pageiget our DPiput into DP register

-MoveTo #125i#125-DraWString #ClearLine iyes, I'm lazy - these are spaces-MoveTo #20i#125-DrawString #SelectStrNDrawString MemberHandle

PushLong W1PtrSetPort

phapha ilong word result space

GetPortPullLong OldGrafPort

Page 8Vol. 1 NO.7

irestore DP for TaskMaster

iget the pointer the handle points to#2[MyDP] , Y

[MyDP]MemberHandleMemberHandle+2

MemberHandleMyDPMemberHandle+2MyDP+2

rts

PushLong OldGrafPortSetPort

pld

ldyldataxldastastx

plastaplasta

phapha iresult spacePushLong #0 isearch from beginningPushLong #ListRecord ipass list record location

NextMember iscan list for selected item

796797798799800801802803804805806807808 :cont809810811812813814815816817818819820821822823824825826827828829830831832833834

%eSourceror SJ2Lpprentice

In lines 801 to the end I indulge in some weirdness because I want to find and displaythe actual text of the selected item. If you go back to the item record section, you 'n seethat an item record contains a pointer to the actual string data. Hmmm ... if_NextMember returns a pointer which points to a pointer, doesn't that make the valueit returned a handle? Yes. in a manner of speaking. And no - you only need to considerit a handle jf you're looking for the. string data like I did above. In that case, Idereferenced it and used the result to print some text.

A reasonable alternative might be to make your item records 6 bytes long and use theextra byte to hold the number of the item. The value returned by _ NextMembe r plus 5would yield the item number. Hence the new structure:

* Item Records

MyListADRL Item1DFB 0DFB 1

icontains address of stringirequired flag byteiitem number

Vol. 1 NO.7 Page 9 %e Sourcerors .9Lpprentice

ADRLDFBDFBADRLDFBDFB

Item2o2Item3o3

;item number

iand so on up to listSize ...i item number

And the new code:

797798799800801802803804805

phapha iresult spacePushLong #0 isearch from beginningPushLong #ListRecord ;pass list record location

NextMember iscan list for selected item

PullLong MemberPointerlda MemberPointer+5 iretrieves item number selectedsta ItemSelected

Remember that ifyou change the size of the item records, you also need to update yourlist record such that listMemSize is set equal to the correct size.

GS assembly code seems to be self-replicating at times. A simple procedure can easilyexpand into 500+ lines, or so it goes for me. I found it refreshing to discover that I couldmake use 'of the list display capabilities in the toolbox with such· a small expenditure oftime and energy. I hope you can make use of this, too.

- Ross

An o iGinal LetterBy Steve Stephenson

Editor: It is probably hard to appreciateSteve's idea here on nested ORCs unless you'veever had to write code that required it. I had acontract job once that required some customquit code for ProDas 8. The tricky part wasthat I had to install different versions basedon the type of host machine (yuk) , hence I hadto write code that would be loaded at $2000+,relocated to the dispatcher space, and thenpulled down and run at $1000. Since therewere several versions (all of which had to beaRCed at $1000), it got messy. Steve's ideaswould have helped me a lot way back when.

Dear Ross,

The other day one of my friends asked meabout nesting orgs with Merlin. I have hadsome experience in that area and whipped upthis little code fragment and uploaded it to ourlocal BBS for him. Later I realized that this isan area of Merlin that leaves a little to bedesired and that it is not adequately treated inthe documentation; just the kind of thing toshare with others who may run into the samesituation. The end result is this letter and thecode that might interest you...

%e Sourcerors !lLpprentice Vol. 1 No.7 Page 10

First of all, the situation: You are writing aprogram that will sit on the disk in a singlefile: it has several sections that will be movedto other areas of memory (other than where itis loaded) at runtime; some of these sectionsneed to be modified for some reason (perhapsfor different computer models); you aretherefore trying to reference those areas atruntime.

Now the problem: Although Merlin supportsthe concept of ORG ADDR to let the varioussections attain their respective runtimeaddresses, the only pseudo op that Merlin hasto return to the previous address is ORG. Andactually that is a misnomer; ORG does NOTreturn the PC address back to the previousaddress (prior to ORG ADDR), instead it returnsthe PC to an address relative to the INITIALORG. This is very similar conceptually to theBasic.System GETBUFR and FREEBUFR inthat you may incrementally go deeper with theGETBUFR call, but FREEBUFR pops ALL.Merlin's method is entirely satisfactory if youonly want to change the address once and comeright back, but you need another method tonest more than one level with any degree offlUidity.

The solution: Don't use ORG; instead alwaysuse ORG ADDR. How simple! Gee, wish I hadthought of that... but no so fast. How do youknow what address to use? Well, the method Iuse is to calculate and reset back to theprevious level's relative address when I finisha nested section. To calculate the address, youwill need three labels. I always name thesection (PRIOR to the re-ORG) so I have an

address that is relative to the previous section.The re-ORG it wherever you need (usingabsolutes or constants). Then insert anotherlabel for the start of the section; this one willbe relative to the nested section's addresses.After the code of the section, add another labelas an end marker (also relative to this section).To calculate for the reset, subtract the endmarker from the beginning marker todetermine the number of bytes used and addthat to the address that existed prior toentering this section. What you will have is theaddress that you would have had if you'd notchanged the ORG,

Referring to the source code will make thisMUCH clearer. ..

On a totally different subject... I have encloseda disk with a program I put together for fellowMerlin-16 programmers. I thought you andyour readership might be interested. Feel freeto do whatever you wish with it.

Sincerely,

Steve Stephenson

Full-time, Independent, Free-lance Apple IIAssembly Language Programmer (Currentlyspecializing in the IIGS)

Editor: The program Steve was referring to iscalled Dialog Maker. It is an exceptionalpublic domain dialog creation utility whichgenerates Merlin 16 source. I'll put it on thequarterly disk and copy it for anyone thatsends me a disk and SASE.

tr adrorg $1000

Start:a nop ;$1000:b nop ;$1001

nest1 ;$2002 ($1004)org $3000

n€st1:beg ;$3000:a nop ;$3000 ($2002) ($1004):b nop ;$3001 ($2003) ($1005)

1000: EA1001: EA

2000: EA2001: EA

3000: EA3001: EA

2 *=================================================3 * How to run nested orgs with Merlin4 *=================================================5

67

8

910 *-------------------------------------------------11 zl ;$100212 org $200013 zl:beg ;$200014:a nop ;$2000 ($1002)15:b nop ; $2001 ($1003)16 *-------------------------------------------------1718192021

Vol. 1 No.7 Page 11 %e Sourcerors .9lpprentice

Elapsed time = 14 seconds.

End Merlin-16 assembly, 14 bytes, 0 errors, 53 lines, 11 symbols.

=$3002=$2000

($1008)($1009)($100a)

NEST2Zl:BEG

Zl:END =$200ANEST2:BEG=$4000

;$100c;$100d

; $2008 ($100a); $2009 ($100b)

; $3002 ($2004) ($1006)

NEST1:END=$3006Zl =$l002

NESTl =$2002NESTl:END=$3006

nopnop

nopnop

=$2000=$3002

:a:bzl:end* $200a-$2000 = $a + $1002 = $100c

org zl:end-z1:beg+z1*-------------------------------------------------

Reality:a:b

: a n op ; $3004 ($ 200 6): b nop ; $3005 ($2007)nest1:end ;$3006 ($2008)* $3006-$3000 = 6 + $2002 = $2008

org nest1:end-nest1:beg+nest1*-------------------------------------------------

*-------------------------------------------------

*-------------------------------------------------nest2

org $4000nest2:beg ;$4000:a nop ;$4000 ($3002) ($2004) ($1006): b nop ; $ 4001 ($3003) ($ 2 005) ($1 007 )nest2:end ;$4002 ($3004) ($2006) ($1008)* now to "un" org back one level, ~ount up the number* of bytes at this nested level and add the address* of the beginning of the nested area (using address* relative to previous level). In this case,* nest2:end - nest:2beg {$4002-$4000} = 2 bytes,* nest2's address is $3002, so the next pc address* will be $3004

org nest2:end-nest2:beg+nest2*-------------------------------------------------

NEST1:BEG=$3000NEST2:END=$4002

Zl:BEGNEST2

2223242526272829303132333435363738394041424344454647484950515253

NESTl =$2002NEST2:BEG=$4000Zl:END =$200A

Zl =$1002NEST1:BEG=$3000NEST2:END=$4002

100e: EA100D: EA

Symbol table, alphabetical order:

2008: EA2009: EA

3004: EA3005: EA

Symbol table, numerical order:

509/ 923-2025

•Inglis98846

I•1Box 398Pateros, WA

rrhe Sourceror's .9LpprenticeCopyright © 1989 by Ross W. Lambertand Ariel PublishingAll Rights Reserved

Subscription prices in US dollars (Canadian andMexican subscribers add $5 per year, all othernon-North American subscribers add $15 peryear):

subscription payment at any time. MY LIABILITYFOR ERRORS AND OMISSIONS IS LIMITED TOTHIS PUBLICATION'S PURCHASE PRICE. In nocase shall I or my contributors be liable for anyincidental or consequential damages, nor for ANYdamages in excess of the fees paid by asubscriber.

Please direct all correspondence to:

Ross W. Lambert.... Editor & PublisherTamara Lambert..... SubscriptionsJay Jennings, Eric Mueller, RobertMoore Tech EditorsRebecca Lambert... Stamp licking

WARRANTY and LIMITATION of LIABILITY

I warrant that the information in fJ'/ie J'lpprenticeis correct and somewhat useful to somebodysomewhere. Any subscriber may ask for a fullrefund of their last

1 year ...$28 2 years...$52 Ariel PublishingP.O. Box 398Pateros, WA 98846

5091 923-2025

fJ'lie Sourceror's J'lpprentice is a product of theUnited States of America.

We here at Ariel Publishing freely admit ourshortcomings, but nevertheless we strive to bringglory to the Lord Jesus Christ.

Apple, Apple II, IIgs, BASIC.SYSTEM and ProDOS areregistered trademarks of Apple Computers, Inc.