Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2.programmer > #2003
| Newsgroups | comp.sys.apple2.programmer |
|---|---|
| Date | 2015-12-11 18:02 -0800 |
| References | <n4es54$pps$1@dont-email.me> |
| Message-ID | <cd6052b8-32a3-4cf2-b1cb-81831ed61409@googlegroups.com> (permalink) |
| Subject | Re: Secret Shame? Reading Source Code |
| From | wssimms@gmail.com |
Am Samstag, 12. Dezember 2015 01:06:18 UTC+9 schrieb ultramagnus_tcv: > Hey folks, > > I come before you humbled by the fact that I have no idea how to read > source files. Oh, I can read English and I have a passing familiarity > with 6502 assembly, but I don't understand some (basic?) things about > it. > > I have a few questions and I hoped I could be set straight on: > > 1. Are the numbers on the left typical of where the program resides in > memory rather while running than on disk? They are a running count of locations used by the object code. They may or may not have anything to do with where the code will reside in memory. > 2. If there is no accompanying information with the source, how does > one figure out what assembler was using to write the code? For > instance, does Apple always use EDASM? (I did most of my studies in > Merlin.) Usually you guess based on the specifics of the syntax. It is usually fairly straightforward to translate a given piece of code for any assembler. If all you are do is reading, it doesn't really matter that much anyway. > 3. If one were a masochist, could one enter the hexadecimal values on > the left into, say, the monitor? Yes, but unless everything is at the correct location, it probably won't run correctly. > 4. I've been told that you can't merely identify the assembler used and > then re-type the code into that assembler and expect it to assemble > and/or run. Why would that be? Actually that should work just fine, provided you really have all of the source code. It is entirely possible that you don't have macro libraries, etc. In which case, you would need to recreate the macros before you could assemble the source. > I apologize if these are dumb questions. As I investigate the Apple > ///, I often find people refer me to the source. But if I can't read > it.........? I agree with Chris. You need to study a bit more. Given that you already have some familiarity with assembly code, you shouldn't find it very difficult to get up to speed.
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Secret Shame? Reading Source Code ultramagnus_tcv <mikew@thecomputervalet.com> - 2015-12-11 10:06 -0600
Re: Secret Shame? Reading Source Code Chris Torrence <gorthmog@gmail.com> - 2015-12-11 08:50 -0800
Re: Secret Shame? Reading Source Code ultramagnus_tcv <mikew@thecomputervalet.com> - 2015-12-12 08:38 -0600
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2015-12-12 16:04 -0600
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2015-12-12 16:10 -0600
Re: Secret Shame? Reading Source Code ultramagnus_tcv <mikew@thecomputervalet.com> - 2015-12-13 10:21 -0600
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2015-12-13 11:23 -0600
Re: Secret Shame? Reading Source Code ultramagnus_tcv <mikew@thecomputervalet.com> - 2015-12-13 11:41 -0600
Re: Secret Shame? Reading Source Code dempson@actrix.gen.nz (David Empson) - 2015-12-14 08:15 +1300
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2015-12-13 17:16 -0600
Re: Secret Shame? Reading Source Code Jeff Blakeney <CUTjeffrey_blakeney@yahoo.ca> - 2015-12-13 18:17 -0500
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2015-12-13 17:39 -0600
Re: Secret Shame? Reading Source Code m.omalley.au@gmail.com - 2016-01-24 02:26 -0800
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2016-01-24 10:45 -0600
Re: Secret Shame? Reading Source Code wssimms@gmail.com - 2016-01-24 15:20 -0800
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2016-01-24 23:33 -0600
Re: Secret Shame? Reading Source Code wssimms@gmail.com - 2016-01-25 05:01 -0800
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2016-01-25 16:29 -0600
Re: Secret Shame? Reading Source Code michael.pohoreski@gmail.com - 2016-01-27 07:09 -0800
Re: Secret Shame? Reading Source Code wssimms@gmail.com - 2015-12-11 18:02 -0800
Re: Secret Shame? Reading Source Code awanderin <awanderin@gmail.com> - 2015-12-11 23:01 -0700
Re: Secret Shame? Reading Source Code Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-01-28 12:33 -0800
Re: Secret Shame? Reading Source Code Michael Barry <barrym95838@yahoo.com> - 2016-01-28 22:50 -0800
Re: Secret Shame? Reading Source Code wssimms@gmail.com - 2016-01-29 02:04 -0800
Re: Secret Shame? Reading Source Code Michael J. Mahon <mjmahon@aol.com> - 2016-01-29 13:58 -0600
Re: Secret Shame? Reading Source Code Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-01-29 16:10 -0800
Re: Secret Shame? Reading Source Code Michael Pohoreski <michael.pohoreski@gmail.com> - 2016-01-29 16:15 -0800
Re: Secret Shame? Reading Source Code Brian Patrie <bpatrie@bellsouth.spamisicky.net> - 2016-01-31 03:50 -0600
Re: Secret Shame? Reading Source Code michael.pohoreski@gmail.com - 2016-01-25 11:03 -0800
Re: Secret Shame? Reading Source Code michael.pohoreski@gmail.com - 2016-01-25 11:04 -0800
Re: Secret Shame? Reading Source Code michael.pohoreski@gmail.com - 2016-01-27 07:14 -0800
Re: Secret Shame? Reading Source Code ultramagnus_tcv <mikew@thecomputervalet.com> - 2016-04-29 19:33 -0500
csiph-web