jmarvin@oracle.com (08/01/90)
*********** There's been a lot of questions on getting started programming on the Amiga. Each programmer is unique, but I'ld like to share things I found useful. I've got 'C', LISP, and Prolog info: 'C': The best book I found to start 'C' with is: Learning to Program in 'C' Thomas Plum, Prentice Hall ISBN 0-13-527847-3 The best 'C' book on how to do Amiga specific stuff (I recommend learning 'C' first, then trying windows, sounds, graphics, etc.): Amiga 'C' for Advanced Programmers Bleek, Jennrich, & Schulz, Abacus ISBN 1-55755-046-8 My favorite compiler: Manx, Aztec 'C', with source level debugger The best 'C' tool: Lint for the Amiga Gimple Software 3207 Hogarth Lane Collegeville, PA 19426 215/584-4261 If you don't know, lint finds bugs in your source that even good ANSI 'C' compilers will never tell you about. Ever do this? if (a = b) ... When you wanted this? if (a == b) ... lint will flag this with a warning. ********* LISP: My favorite Amiga Lisp: LISP McCauley Software Systems P.O. Box 271031 Houston Texas 77277-1031 713/630-0647 I've tried Metacomco's Cambridge Lisp (yuch!!!) and xlisp. This supports more of Common Lisp and some Amiga graphics. ********* Proglog: The ONLY Prolog I know about: UNH Prolog University of New Hampshire Dept. of Computer Science Sorry, the address is not on the manuals! A little long distance directory assistance should get you the university, then ask for the computer science desk. ********* Notes: I used McCauley LISP and UNH Prolog for AI coursework at Cal State University, Hayward (Hay U!). No monster programs, so I can't judge how they'll do under a heavy load. Both are interpeters only. I've done *lots* of 'C' with my Manx compiler and Gimple's lint. They are both professional products. I've also heard good things about Lattice. I can say the Manx source level debugger is good, it lets you debug graphics programs since it sends graphics calls to another screen (as opposed to drawing over your debug session!). It comes with lots of UNIX(tm) type utilities (grep, du, cat, vi, ...) and can be set up to have the compiler use Arexx to load your editor with the file an error occurs in and jumps to that line. Their vi editor clone (z) supports Arexx. If you're just learning 'C' now, my advice is use an ANSI compiler! You'll let the compiler find the bugs, not you durring run time! Use functional prototypes. This will catch lots of bugs that old (K&R) compilers will just guru on! Lint will catch even more bugs. ******************************************************************* * Nhoj Nivram * * email: jmarvin@oracle.com * * "Reality is a Harsh Mistress..." * *******************************************************************