[Coco] VCC - Becker Module (Was: Basic09 6309 version)

[Bill Pierce]

James, that's one of the MANY reasons we moved away from VS6 to start with. There are so many things that are unsupported in VS6 and available with single cmds in VS2015. VS6 just can't handle things well for win7-10 targets, whereas in vs2015, we can target Winxp and up. When we started trying to update VCC, it was due to people having many problems in win10 which was resolved by just moving it to vs2015 with almost no changes. VS6 is no longer available in any form making it impossible for future developers to pick up were ever we leave off. There's only a handfull of people who even have the old VS6 compilers. Moving to modern developmant systems keeps the project moving forward.

 

 

Bill Pierce
"Charlie stole the handle, and the train it won't stop going, no way to slow down!" - Ian Anderson - Jethro Tull

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page

E-Mail: ooogalapasooo at aol.com

 

 

-----Original Message-----
From: James Ross <jrosslist at outlook.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Tue, Jun 6, 2017 12:44 am
Subject: Re: [Coco] VCC - Becker Module (Was: Basic09 6309 version)

Walter Zambotti wrote: > I have now tested my built version with the DIVQ instructions > with the DW starter kit and the becker port appears to be working!That is cool Walter!! > ... with the only changes being:> 6309 DIVQ instructions added to hd6309.cgot those. Thanks man! -- you did great on that fix, btw. > #include <stdbool.h> added to becker.cThe other way to fix that, which is backward compatible w/ older C’s is to change the bool, boolean, true, false keywords to BOOL, TRUE, FALSE …  throughout the module + some other places in that module where you have to move the definition of a local variable to the top of the function.  Then it compiles fine also w/o that header which does not exist in VS6.I know my instance on VCC source maintaining compatibility w/ VS6 is strange and/or weird, but so is messing around w/ a 35 year old computer, when you really get down to it!! Ha! :)I’ll be updating my fork on GitHub w/ the code as soon as I can figure out what is going on w/ VS6 not liking it at runtime regardless what. James-- Coco mailing listCoco at maltedmedia.comhttps://pairlist5.pair.net/mailman/listinfo/coco