[Avrora] API chaos
Ben L. Titzer
titzer at cs.ucla.edu
Wed Nov 16 12:14:29 PST 2005
Just a heads up to those of you who are doing development in Avrora
(device implementations, monitors, new platforms, etc). There have
been some pretty significant movements of code around the past few
days and over the next week there will continue to be some (limited)
chaos. I am restructuring the simulator internals to be architecture-
agnostic in preparation for integrating the MSP430 support. As a
result, there are already some new interfaces and some of the legacy
stuff has been moved out of the simulator core and some interfaces
have cropped up in their place.
Most of the code that just uses monitors and such should not need any
major retooling; however they may need to import code from different
packages (e.g. avrora.core.Instr has moved to
avrora.arch.legacy.LegacyInstr). Also, the avrora.sim.State interface
has been reduced to only a few methods since it will have to
generalize all architectures. You can still cast these instances to
LegacyState if necessary (for example to access the current
The legacy stuff (avrora.arch.legacy) will eventually be supplanted
in favor of the new AVR and MSP430 support (avrora.arch.avr and
Sorry for the inconvenience, but the necessary eggs are being broken
in the glorious pursuit of omelets.
Eventually things will stabilize at a (hopefully) much cleaner and
natural level of abstraction that does not place undue indirection
burdens on developers.
Before we work on artificial intelligence, why don't we do something
about natural stupidity?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Avrora