[Coco] Drivewire and ADOS...

[Christopher Smith]

Yes, Windows is not my favorite thing in the world to work with, but I've done it.  I have a current install of the free version on one of my systems at home in case I ever want to write something with it.  That hasn't happened in quite a while. :)

Chris

----- Original Message -----
> From: "Bill Pierce" <ooogalapasooo at aol.com>
> To: coco at maltedmedia.com
> Sent: Tuesday, October 1, 2013 3:32:42 PM
> Subject: Re: [Coco] Drivewire and ADOS...
> 
> 
> Chris, have you done any work in MS Visual C++?
> 
> Bill Pierce
> 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: Christopher Smith <csmith at wolfram.com>
> To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
> Sent: Tue, Oct 1, 2013 4:28 pm
> Subject: Re: [Coco] Drivewire and ADOS...
> 
> 
> I do most of my code in C, actually.  At other times, C++, Objective
> C (there's
> a bit of a theme here I guess), Java, Forth, Scheme, Perl, Python,
> and -- well,
> some others. :)  What assembly I've done is often inlined into C
> code, actually.
> Last time because I wanted to take command-line arguments and convert
> them into
> an arbitrary function call to an arbitrary dynamically loaded
> library.  C
> doesn't have a built-in facility for doing that but it's easy to
> arbitrarily
> construct a standard call on the stack with a few assembly
> operations. ... but
> as for Java, I have done a few personal projects with it and worked
> on probably
> two projects for a small commercial software house that used it.
> 
> No, it's not really a language for the CoCo, though there are
> possibilities.
> Google tells me the CLDC requires only about 160k of memory at a
> minimum.  There
> are some assumptions built in about the code-size of the interpreter,
> so you
> could perhaps get by with less.  It also "requires" a 16 bit
> processor, but I
> suspect what they really mean is that you must be able to perform 16
> bit numeric
> operations.  It seems feasible to cram a CLDC/MIDP1.0 (I say 1.0
> because they
> didn't add floating point math until 2.0, though if it did support
> 2.0 you could
> run Angry Birds) system in 512k of RAM on an upgraded CoCo 3,
> emulating the
> 16-bit numerics and using drivewire for its required network
> connection.  Of
> course this would be a huge project of limited usefulness, and
> probably isn't
> the right way to get anything on the CoCo, but it would be hilarious
> if it could
> run Java code. :)
> 
> Chris
> 
> 
>  
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
> 

-- 
Christopher Smith
Systems Engineer, Wolfram Research