[Coco] 64k memory limit (was) CP/M emulator for OS9/6809

[Bill Pierce]

Tormod, the only problem with using "version control" on the MShell code is that it's in 99% OS9 C code being compile on the Coco under OS9. I don't think they make a "Mercurial-09 6809". I'm hoping those people working on the "6809 C cross-compiler" project are making progress, as it's really needed. The sources to MShell are getting a bit large for the Coco, but still managable.
What's really needed is some "self control"... in making regular backups of the sources.
 
But with all that said, I go it all back going and If I get finished with the parts I'm working on, I may start some public beta testing or maybe even a demo next week. I actually have one beta tester running it and so far, so good :-)
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Tormod Volden <lists.tormod at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sat, May 3, 2014 12:22 pm
Subject: Re: [Coco] 64k memory limit (was) CP/M emulator for OS9/6809


On Wed, Apr 30, 2014 at 12:35 AM, Bill Pierce wrote:
> The beta testing of MShell is no hurry because I broke it today and now I've 
got to fix it LOL
> I was adding some new cool features and all of a sudden it quit working on the 
real Coco, but worked in Vcc... then in trying to isolate that problem, it no 
longer works in Vcc either. I should have it back up and running within the 
week, even if I have to backtrace and remove the new features and get it back to 
what I had it. My last backup was right before I got working again after 2 
mpnths, so I definately don't want to go back that far, though I may have to. 
It's usually the same problem, some rogue pointer sending data into never-never 
land and crashing the system.

I would strongly recommend to learn and use a revision control system
like git or mercurial. For each significant (or as small as you want)
change you'd make a commit, and you will have a nice commented backup
of your development steps. At any time you can rewind to a previous
point and back again. You can for instance test out things on an
experimental branch without messing up the normal development branch.
Just the ability to easily visualize all changes since the last commit
("hg diff" on the command line) makes it so much easier to spot
errors.

Cheers,
Tormod

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco