S?bastien Bourdeauducq wrote: >>In general, it seems to me that you tend to use names that are way too >>generic, which hide the intent and meaning of both the concept and the >>implementation of it in Migen/FHDL.
I'll second this. "Fragment" doesn't convey the right meaning. I've also noticed this with the "fragments" in the PFPU. Took me a while to realize that there was nothing broken about them :) > I could have used "circuit", "module" or "component", but _that_ > would have been too generic :) How about "element", "constituent", "ingredient", ... ? But perhaps we can find something more specific. > As far as I know, Python does not allow you to redefine assignment. Hah ! There are few perversions Python isn't capable of :-) Watch this and tremble: http://svn.openmoko.org/developers/werner/ahrt/host/tmc/lib/instrument.py This is a bit of basic infrastructure for communicating with lab instruments. The idea is that instrument objects can have variables that represent settings of the respective device. So when you set a value, a command may be sent to the device, and if you read one, the value may be retrieved from the device. Or maybe from the cache. Here's some light use in classes representing real instruments: http://svn.openmoko.org/developers/werner/ahrt/host/tmc/lib/meter.py Still working my way through the migen description. - Werner _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
