senior_falcon Posted April 17, 2015 Share Posted April 17, 2015 I have been looking at the possibility of implementing disk access for the XB compiler. I now have the compiler handling the open, close, input and linput, and print to some extent, but there still is a ways to go before that is fully implemented. That's the easy part...The hard part is writing the runtime routines for disk access, and I have neither time nor interest in doing that. If someone is interested in tackling this I can provide information on how to interface with the compiled code - such things as how to pass numbers, strings, commonly used subroutines, workspaces, etc. 2 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/ Share on other sites More sharing options...
RXB Posted April 17, 2015 Share Posted April 17, 2015 I would suggest using the Miller Graphics GPL LINK DSR for full access to all types of devices. (Even Cassette or Hex Tape.) Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3220295 Share on other sites More sharing options...
+Lee Stewart Posted April 17, 2015 Share Posted April 17, 2015 The MG GPLLNK/DSRLNK takes 174 bytes of ALC plus DSRLNK workspace of 32 bytes. I presume we're talking about maintaining the XB/TIB linked list of PABs for open files in graphics mode. It would be dicier if we have to also do it for bitmap mode because the space for PABs is limited in that mode. ...lee Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3220331 Share on other sites More sharing options...
RXB Posted April 17, 2015 Share Posted April 17, 2015 I thought the idea was to maintain compatibility, but if that is not the goal then cross compiling is not the goal. Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3220380 Share on other sites More sharing options...
senior_falcon Posted April 17, 2015 Author Share Posted April 17, 2015 MG GPLLNK is part of the compiler runtime, and I would just put the rest (DSRLNK) of it back in. Bitmap graphics are not a problem because they are not part of XB256. Most of the VDP is available; certainly as much as would be available to XB. 1 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3220414 Share on other sites More sharing options...
Bones-69 Posted April 23, 2015 Share Posted April 23, 2015 * Watching in excitement. Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3224085 Share on other sites More sharing options...
senior_falcon Posted May 17, 2015 Author Share Posted May 17, 2015 Peripheral access for the compiler has been worked out in a limited way: only one file open at a time and DV only. I need to do some thorough testing over the next couple of days to see what has been overlooked, then will post. 5 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3239131 Share on other sites More sharing options...
Opry99er Posted May 17, 2015 Share Posted May 17, 2015 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3239256 Share on other sites More sharing options...
JamesD Posted May 17, 2015 Share Posted May 17, 2015 :) What he said Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3239347 Share on other sites More sharing options...
senior_falcon Posted June 7, 2015 Author Share Posted June 7, 2015 Looks like the programming is pretty much worked out. Limited to Display Variable files, any length you want. 3 files can be open at a time if needed. EOF and error handling are worked out so they work like in XB. I need to come up with a rigorous test to be sure: 1 - the files created by a compiled program are compatible with those created by an XB program. 2 - files created by XB can be read by a compiled program. 3 - the error handling works as expected. 4 - documentation needs to be updated Been very busy but hope to get to this soon. 5 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3252421 Share on other sites More sharing options...
Shift838 Posted June 7, 2015 Share Posted June 7, 2015 This sounds very interesting. Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3252499 Share on other sites More sharing options...
senior_falcon Posted June 15, 2015 Author Share Posted June 15, 2015 Updated compiler with disk access is posted in XB Game Developer's Package, post #1. 5 Quote Link to comment https://forums.atariage.com/topic/237345-disk-access-for-compiler256/#findComment-3257827 Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.