Path: utzoo!attcan!uunet!iconsys!caeco!jose!pedro!pete_ashdown
From: pete_ashdown@pedro.UUCP (Pete Ashdown)
Newsgroups: comp.sys.amiga
Subject: (None)
Message-ID: <312@pedro.UUCP>
Date: 10 Jun 88 02:36:27 GMT
Organization: Bitsko's Bar & Grill, Public Access, Salt Lake City
Lines: 56


In article <55524@sun.uucp> (Chuck McManis) writes: 
  
>A. He wanted to program in Assembly because he wanted to avoid all of the 
>   "library call stuff" that 'C' programs went through to make programs run. 
>   Basically, screw the OS and get right down to the metal. 
  
This is not the case with me.  I have tried to go out of my way to follow the 
guidelines set down by Commodore.  I would rather call the ROM Kernal any day 
than try to set up my own COPPER list for opening the screen. 
  
>B. He had no idea how useful it was to *not* do this, nor how unnecessary 
>   it was for his applications, nor how easy it was to "do it right". 
  
I do realize how useful the ROM Kernal is, but I still haven't found how it is 
"easy."  Indeed, it is much easier than accessing the hardware directly, but 
it still isn't a breeze setting up all the data tables necessary. 
  
>the Amiga is much more complex and difficult to program than the C64, but 
  
I don't know about the C64.  I was on the Apple //+ before the Amiga.  I 
jumped from BASIC to 6502 because my highschool dumped the Pascal class.  To 
this day, I still haven't learned a structured language.  I _tried_ to get 
into 'C', but I found out quickly that I was uneasy not knowing _exactly_ what 
was going on with my program.  I prefer assembly, simply because I feel that 
I am more in control.  Speed has another thing to do with it.  I know 'C' can 
be very fast for some programmers, but I think it would end up being very 
slow code for me, simply because I am a beginner at it.  Above all, I want to 
write games on the Amiga.  After seeing Marble Madness kludge its scrolling, 
I don't think that 'C' is the language I am looking for.  I really haven't 
seen "brilliant game #1" that was written in 'C'.  It also may have something 
to do with the fact that I loaned out my K&R and haven't gotten it back 
yet :-). 
  
>three programs, one that runs from the CLI, one that runs from the CLI 
>or workbench and opens a window, and one that opens a custom screen, 
>gets the information it needs from the system (like where memory is located 
>and how big it is) and then takes over the machince for some killer 
>game. 
  
Thanks for your suggestions.  I may just turn back to examining 'C'.  I have 
already done program #1 to some extent in assembly.  Should I turn back to 
'C' or should I keep going with assembly?  I'd be curious to find out from 
other 68000 assembly programmers (like Mark R.) how they got started. If they 
went from 'C' to assembly or just started out in assembly. 
--- 
|s|  SLACK is neither created nor destroyed!  If you don't have it, its  |S| 
|L| /|__/| somewhere where it shouldn't be! -- Chrch of SubGenius |\__|\ |l| 
|a| \/.|.| <===SPUDS MACKENZIE!  DEMON FROM HELL!  BE WARNED!===> |.|.\/ |A| 
|C| (_/o )  Amiga=Computer  The Police=Music  TrailBlazer=Modem   (o  )  |c| 
|k|    -           [uunet!iconsys!caeco!pedro!slack!pete]          -     |K| 
-- 
\  "I don't practice what I preach because I'm not the kind of person I'm  / 
/    (^:      preaching to."  - J.R. "Bob" Dobbs in Newsweek        :^)    \ 
\ "Like, don't mail me on pedro! I live on slack!" - Pete in a fit of rage / 
/ [uunet!iconsys!caeco!pedro!slack!pete] OR TRY [pete@slack.uucp (I hope)] \