[Coco] [Color Computer] Java for the m6809
James Diffendaffer
jdiffendaffer at yahoo.com
Tue Apr 8 23:55:58 EDT 2008
--- In ColorComputer at yahoogroups.com, "John W. Linville"
<linville at ...> wrote:
>
> On Tue, Apr 08, 2008 at 05:48:17AM -0000, James Diffendaffer wrote:
> > --- In ColorComputer at yahoogroups.com, "John W. Linville"
> > You can't use existing Java code with it (it has NONE of the normal
> > Java APIs).
> > You wouldn't be able to write ANY programs for the coco with it as is.
> > The amount of effort required to do anything on the coco with it is
> > pretty significant.
>
> I can't find my post in the archives where I said "use this to port
> existing Java code to the 6809". Neither can I find the one where I
> said "this is the future of CoCo programming -- start using it today!"
> Could you point them out for me?
Um... post #4152 eluded to it's use for the CoCo. Sorry if I
misunderstood you. Perhaps you were thinking of another CoCo?
> FWIW, I think you are overstating what it would take to make it
> produce a binary to run on the CoCo or a similar device. You would
> still lack the various "standard" APIs, of course.
What you think is irrelevant. What is fact is relevant. The API
provided just has a print routine for a specific LCD display and the
I/O was also for a specific device. To minimum to get that stuff to
work would at least require changing the API to make ROM calls.
You couldn't run any existing Java program but you could at lest print
"hello world".
> "Writing Java Program Proves Frustrating -- Film at 11:00"
Writing all but the most simple Java would cause the program to fail
since it doesn't even support all of Java's built in primitive types.
If you don't use ones that aren't supported and write APIs for what
you want to interface with it *should* be able to spit out an assembly
file.
> I'm tempted to ask how you know it "has everything working" if there
> is no I/O...
I created a hard coded data structure with a subset of an adventure
and the code came from an interpreter that works on at least half a
dozen platforms with minor modifications. I just removed the printf
calls and replaced them with calls to Tim's print routine.
> Oh gosh! You know, you're right...I should have my 1st Amendment
> freedoms revoked for abusing them with such a vile, mean, and angry
> post. It was quite irresponsible for me to suggest that you missed
> the point. Shocking! At least you handled it well...
And I expressed my opinion but of coarse it was "irrelevant" and
"uninformed" because it didn't match yours.
> As for what you missed...you missed that it was just a link to
> a cool project that some might find interesting -- nothing more.
> And you missed the point that crapping all over that guy's project
> because it isn't useful to you just discourages everyone else from
> talking about their own projects.
How dare I say a project isn't very useful because it might disturb
someone that is so sensitive. I guess I should be more politically
correct.
> Is that the best you've got? I suppose all your attempts to paint
> me as some sort of idiot weren't insults? No?
You haven't address ANY technical detail at all but try to paint me as
a hater, uninformed, mean and nasty so I must be wrong.
> Ah yes, easy as pie. I mean, we all have cool projects like this
> just sitting around right?
Heavens no... nobody here has any cool projects sitting around.
<groan>
> We don't just go around bothering the
> group with them! We are all just busy professionals here, trying
> to get through the day so we can get back to our family, friends,
> and hobbies. I'm sorry I bothered you with that silly URL. You can
> go back to your work now.
Want some cheese with your whine?
Why do I feel like I'm having a political discussion with a liberal?
More information about the Coco
mailing list