From: Groepaz (groepaz_at_gmx.net)
Date: 2003-05-05 23:04:03
On Monday 05 May 2003 15:29, Robert Steinmetz wrote:
> > The clock() function will have to be a real kludge. A vanilla Apple
> > II/II+/IIe
> > has no means for generating periodic interrupts. Only with certain
> > peripheral
> >
> > cards can that be done.
just for curiosity, the following
clock_t clock(void)
{
return(0);
}
is a perfectly legal and standard compliant implementation of clock() (the
standard doesnt say how long a clock-tick-period lasts, so it can be anything
from microseconds to milleniums)
now the question is, what about the implementation i have used for some
hackery so far:
clock_t clock(void)
{
static clock_t fake;
return(fake++);
}
i know this is crap hackery :) however, it makes some things work with zero
effort, so does it fit into the standard? :=)
> With the loadable module feature is it possible to do an initial system
> check to load the correct one or to use a config file to load the correct
> one? This would avoid recompiling for each of the countless variations of
> the Apples ][. Of course this may be too complicated or "expensive" to do.
i think thats the best idea for that kinda stuff (although i dont know nothing
about the apple2 so i couldnt say how *much* bloat that would add)
gpz
ps: is it really that the plain apple2 doesnt even have some sort of timer?
(you dont need periodic irq if you have a timer, obviously :=))
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2003-05-05 23:09:58 CEST