Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!bbn!mit-eddie!uw-beaver!tektronix!uunet!iconsys!tom
From: tom@iconsys.UUCP (Tom Kimpton)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Source-level debugging
Message-ID: <233@iconsys.UUCP>
Date: 27 May 88 15:34:10 GMT
References: <1911@rayssdb.ray.com> <2586@polyslo.UUCP> <321@piring.cwi.nl> <2729@polyslo.UUCP> <6010@well.UUCP> <10893@apple.Apple.Com> <2823@polyslo.UUCP>
Reply-To: tom@iconsys.UUCP (Tom Kimpton)
Organization: Icon International Inc., Orem, Utah
Lines: 22

In article <2823@polyslo.UUCP> dorourke@polyslo.UUCP (David O'Rourke) writes:
>In article <10893@apple.Apple.Com> dan@apple.UUCP (Dan Allen) writes:
>>After all, everyone should understand the native language that their
>>machine speaks....
>
>   Why?  What if you use more than one machine.  I currently have to program
>on at least 4 different machines a week.  I thought that this is what high
>level languages were for!

Presumably Dan meant that as a general statement (most declaratives are
general, including this one :-), because generally most developers work
on one machine (family) type.  Knowing the "native" language of the machine
you are on can help you do some short cuts that "higher" level languages
are not implemented to make. For example, if you want to directly manipulate
the current stack frame, there is no way to do it from C.


-- 
Tom Kimpton                    UUCP: {ihnp4,uunet,caeco,nrc-ut}!iconsys!ron
Software Development Engineer  ARPANET: icon%byuadam.bitnet@cunyvm.cuny.edu
Icon International, Inc.       BITNET: icon%byuadam.bitnet (multi-user acct)
Orem, Utah 84058               PHONE: (801) 225-6888