tlm@newton.UUCP (01/09/87)
[munch,munch] I would like to start doing some "serious" programing on my C-64 and have recently gotten the Proline compiler. I would like to throw out some question that I don't believe I've seen on the net yet. 1) Is there any good source of explanation of how the compiler sets up subroutines - local variables, returning variables etc. Do they use an equivelant of csv and cret? Do they try to seperate text and data as much as possible (which is difficult on a 6502)? 2) When you use the cc command incorrectly you get the usage message but the flags it shows are "-pas". I know what 'p' does but I don't see 'a' or 's' mentioned in the rather terse manual provided. 3) How does the memory map for the "shell" go? Once you load a routine is memory it stays resident (well sort of). Does anyone know how it is done? Are ".sh" commands compiled to run at the same load address? If so, how can you have more than one in memory at a time? Well, maybe this will provide for some lively and hopefully useful dialog. p.s. I'm thinking about doing a 4014 emulation using the grafpak package etc. "Just little 'ol me ...." tlm.
bjh@mtgzz.UUCP (01/12/87)
In article <733@newton.physics.purdue.edu>, tlm@newton.physics.purdue.edu (Timothy Lee Meisenheimer) writes: > > 3) How does the memory map for the "shell" go? Once you load a routine > is memory it stays resident (well sort of). Does anyone know how > it is done? Are ".sh" commands compiled to run at the same load > address? If so, how can you have more than one in memory at a time? You can specify any starting address, but the default creates a .sh file. All .sh files load at the same address, so only one can be resident. It is possible to load and a run a .sh file, then use a command that is part of the resident shell, and then run the .sh again without reloading. Anyone have more details on the memory map ? ......BJ