On Thu, 23 Sep 1999 21:30:14 -0230 "Andrew Vardy" <avardy@roadrunner.nf.net> writes: > If I take a source code file (let's assume in ebud) and use the > pseudo-op > > .dis > > Then the assembler produces output, generally with all > instructions, and everything that runs through. I like to also > divert > this output to a file, via, for example, the typical: > > open 9,9,9,"file,s,w":cmd 9 > > as > > And so forth. Works fine. > > I like to produce this file. But I have a problem when the source > code uses includes for other source code. Like if I use the ".seq" > pseudo-op to include some other source code files. In this case, > suddenly my '.display' is not going out to disk file. (I can't > quite > remember all the particulars now.) > > Does anyone have any idea how to make it work? > My best guess would be that Buddy uses the KERNAL CLALL function call in between the .seq directives and it will close all files, including the one you created during assembly. However, pseudo ops can be user defined in Buddy. Just program a pseudo op to open a disk file at the start of each .seq file, or open the master disk file and add to its contents. I don't know how to create a pseudo op, though. I'll have to dig through the etext version of the Buddy manual. -Todd Elliott ___________________________________________________________________ Get the Internet just the way you want it. Free software, free e-mail, and free Internet access for a month! Try Juno Web: http://dl.www.juno.com/dynoget/tagj. - This message was sent through the cbm-hackers mailing list. To unsubscribe: echo unsubscribe | mail cbm-hackers-request@dot.tcm.hut.fi.
Archive generated by hypermail 2.1.1.